Endearhq Endear API

Name: Endear API
Brand: Endear API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey, bearer6 EndpointsREST

For Agents

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

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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

GET STARTED

Start building with Endear API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Endear API keys and bearer tokens are stored in Jentic's encrypted vault. Agents receive scoped credentials at execution time so secrets never appear in the model's context.

Intent-based discovery

An agent searches by intent (e.g. 'create a retail customer') and Jentic returns the right Endear REST or GraphQL operation with its input schema.

Time to first call

Direct Endear integration: 1-2 days to handle dual-auth, GraphQL client setup, and bulk import retries. Through Jentic: under 1 hour — search, load, execute.

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 at https://app.jentic.com/sign-up.

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.

Endearhq Endear API

Connect the Endear API to your agent

Capabilities

Start building with Endear API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs