Ellipsend API

Name: Ellipsend API
Brand: Ellipsend API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact Managementoauth224 EndpointsREST

For Agents

Track contact-level activities, products, statuses, and labels in Ellipsend. Authenticated via OAuth 2.0 against api.ellipsend.com.

Install Jentic One Beta

Connect the Ellipsend API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ellipsend 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 Ellipsend API.

Create and retrieve activities tied to contacts via /activity

Manage a product catalogue with full CRUD on /products

Configure status pipelines using /statuses to track work stages

Tag activities and contacts with reusable labels via /labels

GET STARTED

Start building with Ellipsend API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Ellipsend API, keeping it validated and agent-ready. Ellipsend is an activity-management and lightweight CRM platform with a 24-endpoint REST API covering activities, products, contacts, statuses, labels, and assignees. Authentication uses OAuth 2.0 with explicit register, token, and refresh endpoints, and all calls hit https://api.ellipsend.com/v1. Resources are designed around tracked activities — each activity ties to a contact, a status, a set of labels, and an assignee.

Use Cases

Patterns agents use Ellipsend API for, with concrete tasks.

★ Activity Tracking and Routing

Operate a sales or service team's activity log inside Ellipsend by creating activities on contact, applying status pipelines, and assigning to the right team member. The /activity, /statuses, and /assignees endpoints together form a minimal task-routing surface, and labels add reusable tagging without schema changes. Suitable for teams of up to a few hundred users.

Create an activity of type 'follow-up call' for contact_token=xyz, set its status to 'in-progress', label it 'priority', and assign it to assignee_id=12

Product Catalogue Sync

Sync a product catalogue from an upstream system (ERP or e-commerce platform) into Ellipsend so activities can reference the correct product. The /products endpoints support full create, update, and delete, which lets a daily sync job mirror the source of truth idempotently.

List existing products in Ellipsend, diff against the ERP product list, and POST any missing products before deleting items the ERP no longer sells

OAuth Onboarding for an Integration

Build a multi-tenant integration that lets each Ellipsend customer authorise the app once via /auth/register and /auth/token, then refreshes tokens with /auth/refresh on schedule. Storing only the refresh token externally keeps the access-token blast radius small, and the company-info endpoint lets the integration label connections cleanly.

Exchange the registration credentials at /auth/token, store the refresh token, then call /company to label the connection with the workspace name

AI Agent Integration via Jentic

Build an AI agent that scans email threads for follow-up commitments and creates matching activities in Ellipsend with the right contact, label, and assignee. Through Jentic, the agent searches by intent, loads the activity schema, and executes without holding the OAuth tokens in its prompt.

Search Jentic for 'create an activity for a contact', load the schema for POST /activity, and create a follow-up activity from the latest email thread

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/activity

Create an activity

GET

/activity-types

List activity types

POST

/products

Create a product

PUT

/contact/{token}

Update a contact

POST

/statuses

Create a status

POST

/labels

Create a label

POST

/auth/token

Get an OAuth access token

POST

/activity

Create an activity

GET

/activity-types

List activity types

POST

/products

Create a product

PUT

/contact/{token}

Update a contact

POST

/statuses

Create a status

POST

/labels

Create a label

Why Jentic?

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

Credential isolation

Ellipsend OAuth tokens are stored encrypted in the Jentic vault (MAXsystem). Refresh is handled automatically so the agent never sees raw access or refresh tokens in its context.

Intent-based discovery

Agents search by intent (e.g. 'create an activity for a contact' or 'add a product') and Jentic returns the matching Ellipsend operation with its input schema, so the agent does not have to map the 24-endpoint surface manually.

Time to first call

Direct integration: 1-2 days to implement the OAuth dance, refresh logic, and resource mapping. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Ellipsend API through Jentic.

Why is there no official OpenAPI spec for Ellipsend API?

Ellipsend publishes its API reference as HTML at api.ellipsend.com/v1/docs rather than as a versioned OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call Ellipsend 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 Ellipsend API use?

Ellipsend uses OAuth 2.0. Get a token at POST /auth/token, refresh it at POST /auth/refresh, and register new app credentials at POST /auth/register. Through Jentic, both the access and refresh tokens are stored encrypted in the vault and never appear in the agent's prompt.

Can I create an activity for a specific contact?

Yes. POST /activity creates an activity and accepts the contact reference, activity type, status, labels, and assignee in the body. Use GET /activity/{id} afterwards to confirm the persisted record.

How do labels and statuses differ in Ellipsend?

Statuses model the stage of an activity in a workflow (one status per activity at a time), while labels are reusable tags that can be applied freely. Both have full CRUD endpoints under /statuses and /labels.

How do I create an activity through Ellipsend via Jentic?

Run the Jentic search query 'create an activity for a contact', load the input schema for POST /activity, then execute. Jentic injects the OAuth bearer token at execution time, so the agent does not need to manage the token lifecycle.

Is there a way to update a contact without their internal ID?

Yes. PUT /contact/{token} takes a contact token rather than a numeric ID, which makes it safe to share with web forms and embedded widgets that should only update one specific contact.

Ellipsend API

Connect the Ellipsend API to your agent

Capabilities

Start building with Ellipsend API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs