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.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Ellipsend operations and credentials the agent may use, and it can only call what you explicitly allow. You can grant read access to activities and activity types while withholding write operations, so creating activities, products, statuses, or labels are not included unless you add them. Since Ellipsend puts the contact token in the URL path at PUT /contact/{token}, a rule can pin the agent to updating a single contact rather than any record.