Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / CRM / Endear API
Endear API logo

Endearhq Endear API

67
AI ReadinessAI-Aware (B)67/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCRMContact ManagementapiKey, bearer6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Look up, create, and bulk-import retail customer records in Endear via REST endpoints, or run arbitrary queries against the GraphQL endpoint.

Use for: I need to import a CSV of new customers into Endear, Find a retail customer by ID in Endear, Create a customer record for a new in-store shopper, Update the email address on an existing customer profile

Not supported: Does not handle order processing, inventory, or marketing campaign sending - use for retail customer record management and clienteling lookups only.

Jentic publishes the only available OpenAPI specification for Endear API, keeping it validated and agent-ready. Endear is a retail-focused CRM and clienteling platform; the API exposes both a GraphQL endpoint for full schema access and a small REST surface for customer create, read, and bulk import operations. Retail teams use it to sync customer records from POS and e-commerce systems and to keep clientele data current. The API is ideal for agents that need to look up or update customer profiles tied to retail transactions.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Endear API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Endear API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fendearhq.com%2Fendear" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fendearhq.com%2Fendear" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Endear API.

Query customer records via the GraphQL endpoint for arbitrary field selection

List customers using the REST customers endpoint for simple integrations

Create or update a customer profile from a POS or e-commerce sync

Update an existing customer's attributes by ID

Bulk-import customer data from a CSV or external system

Use Cases

Patterns agents use Endear API for, with concrete tasks.

★ POS-to-CRM Customer Sync

Push new customers captured at point-of-sale into Endear so the CRM stays current. POST /customers creates or updates a record idempotently, and POST /integration/import handles bulk batches at the end of a shift. Stores running on Shopify or Lightspeed can use this to mirror their customer database into Endear without manual export.

Import a JSON array of 250 new customer records from yesterday's POS export into Endear via the bulk import endpoint

Clienteling Lookup

When a sales associate asks 'what does this customer like?', an agent can call GET /customers/{id} to pull the customer profile and use the GraphQL endpoint to fetch related order history in a single round trip. This powers in-app recommendations during a store visit.

Look up customer with id 'cust_4821' and return their email, name, and the last five orders via a GraphQL query

Profile Maintenance

Use PUT /customers/{id} to update fields such as email, opt-in status, or store affiliation in response to a customer service event. This keeps the CRM accurate without requiring a full re-import.

Set the email_marketing_opt_in flag to false on customer id 'cust_889' and confirm the update

Agent-Driven Retail Workflow

An AI agent handling retail back-office tasks searches Jentic for 'create a retail customer', loads the Endear POST /customers schema, and executes the call. This lets the agent stitch together POS events, marketing platforms, and Endear without bespoke client code per integration.

On a new POS event, create the customer in Endear via POST /customers and store the returned id back on the order

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for endear api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/graphql

GraphQL endpoint for queries and mutations

GET

/customers

List customers

POST

/customers

Create or update a customer

GET

/customers/{id}

Get customer by ID

PUT

/customers/{id}

Update a customer

POST

/integration/import

Bulk import customer data

POST

/graphql

GraphQL endpoint for queries and mutations

GET

/customers

List customers

POST

/customers

Create or update a customer

GET

/customers/{id}

Get customer by ID

PUT

/customers/{id}

Update a customer

POST

/integration/import

Bulk import customer data

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

E

Endear API

- AI-Aware (B)
67/100
81
Foundational Compliance
57
Developer Experience & Jentic Compatibility
49
AI-Readiness & Agent Experience
94
Agent Usability
63
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
81

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

25%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

57

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

29%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

49

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4
38%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

63

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
62%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Endear API by hand means choosing between its X-API-Key header and bearer auth, mixing REST customer routes with a /graphql endpoint, and building your own error handling against https://api.endearhq.com. Through Jentic you install once, import the Endear API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The Endear API puts the customer id in the URL path (/customers/{id}), so a rule can pin your agent to one customer record: it can read and update that customer and nothing else. You choose the operations it may call, so ones like creating customers or running an integration import are not included unless you add them.

Credential isolation

Your Endear credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'look up a retail customer record' or 'update a customer profile', and Jentic returns the matching Endear operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

EngageBay CRM REST API

→

EngageBay is a general-purpose CRM with marketing and sales modules; Endear is retail-specific clienteling.

Choose EngageBay for general B2B/B2C CRM tasks; choose Endear when the use case is retail clienteling and POS-tied customer profiles.

Complementary

Engage.so API

→

Engage.so handles user messaging and event tracking; Endear holds the retail customer record those messages are sent to.

Use Engage.so to send a campaign or track an event; use Endear to read or update the underlying customer profile.

Complementary

EndorseFlow API

→

EndorseFlow collects testimonials from customers stored in CRMs like Endear.

Pick EndorseFlow when the task is requesting a testimonial; pick Endear when the task is reading or updating the customer record.

FAQs

Specific to using Endear API through Jentic.

Why is there no official OpenAPI spec for Endear API?

Endear does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Endear API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Endear API use?

Endear supports both API key and bearer token authentication. Through Jentic, the credential is stored encrypted in the vault and supplied to the request only at execution time, so agents never see the raw token.

Can I bulk-import customers into Endear via the API?

Yes. POST /integration/import accepts batched customer data in a single call, suitable for nightly POS or e-commerce syncs. For one-off creates use POST /customers instead.

Does Endear expose a GraphQL API?

Yes. POST /graphql is a single endpoint that accepts both queries and mutations, giving the agent flexible field selection beyond what the REST customer endpoints expose.

What are the rate limits for the Endear API?

The OpenAPI spec does not declare rate limits. Treat as workspace-scoped and back off on HTTP 429 responses; check Endear's developer portal for the exact limit on your plan.

How do I sync POS customers into Endear through Jentic?

Run `pip install jentic`, then search 'import retail customers into endear'. Jentic returns POST /integration/import with its input schema; the agent supplies the customer batch and executes against base URL https://api.endearhq.com.

Can I limit what my agent is allowed to do with the Endear API?

Yes. Jentic One runs self-hosted, so your own rules decide which Endear operations the agent may call and which credential it uses. Because the Endear API carries the customer id in the URL path (/customers/{id}), you can pin the agent to reading and updating a single customer record with GET and PUT while excluding everything else. Operations like creating customers with POST /customers or running a bulk load through POST /integration/import are only available if you explicitly grant them.

GET STARTED

Start building with Endear API

Explore with Jentic One
View OpenAPI Document