Agillic API
★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbearer37 EndpointsREST
For Agents
Manage Agillic recipients, run flows, write events, and segment audiences using a bearer-token API surface focused on day-to-day automation tasks.
Use for: Create a recipient with name, email, and consent fields, Update or create a recipient by ID with new attributes, Achieve the 'newsletter_signup' event on a recipient, Execute the welcome flow for a newly registered user
Not supported: Does not handle OAuth2 token exchange, async batch upsert, or promotion evaluation — use the agillic.com surface for those operations.
Jentic publishes the only available OpenAPI specification for the agillic.net surface of Agillic API, keeping it validated and agent-ready. This is the bearer-only slice of the Agillic marketing automation platform, exposing 37 endpoints for managing recipients, one-to-many tables, global data, app push registration, target groups, flow execution, asset uploads, and asynchronous data exports. It is intended for integrations that need a focused subset of the platform without OAuth2 setup, while still authenticating against the same EU1 host.
Install Jentic One Beta
Connect the Agillic API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agillic 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 instanceJentic 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 Agillic API.
Create and update recipients with profile fields and consent state
Read and modify per-recipient one-to-many tables for purchase or preference data
Achieve events on recipients to trigger configured flows
Execute named flows directly to deliver transactional or campaign messages
Manage app push device registration, consent, and unregistration
Run asynchronous exports of recipients, events, and segment data
Discover the schema of person, global, and one-to-many data tables
Use Cases
Patterns agents use Agillic API for, with concrete tasks.
★ Targeted Recipient Updates
Engineering teams write a small set of consent and preference changes back to Agillic from their own data systems. PUT /recipients/{recipientId} performs an update-or-create with the supplied attributes, so a single call handles both new and existing records. Combined with the discovery endpoints, an integration can self-validate the field schema before writing.
PUT /recipients/{recipientId} with marketing_consent=true and updated address fields
Triggering Transactional Flows
Agillic flows can be invoked directly through POST /flows/{flowName}/:execute, suitable for transactional sends like order confirmations and password resets that should not wait for a scheduled segment. Pair the flow execution call with a recipient lookup so the flow runs against the correct profile.
POST /flows/order_confirmation/:execute with the recipient ID and order context
Mobile Push Lifecycle Management
Mobile apps register and deregister devices through the /apps endpoints, while consent toggles ensure users only receive push when they have opted in. The PUT/DELETE structure on /apps/consent/{identifier} makes it easy for a client SDK or backend job to mirror in-app consent state into Agillic.
PUT /apps/register/{identifier} with the device token, then PUT /apps/consent/{identifier} when consent is granted
AI Agent Marketing Tasks via Jentic
An agent can use Jentic to run common Agillic operations — execute a flow, achieve an event, or refresh a recipient — without parsing the spec or storing the bearer token. Jentic injects credentials from the vault and returns the operation's input schema, so the agent assembles a valid request from natural-language input.
Use Jentic to search 'execute an Agillic flow', load the schema, and trigger the welcome flow for a new recipient
Key Endpoints
37 endpoints — jentic publishes the only available openapi specification for the agillic.
METHOD
PATH
DESCRIPTION
POST
/recipients
Create a new recipient
PUT
/recipients/{recipientId}
Update or create a recipient
POST
/recipients/{recipientId}/events/{eventId}/:achieveEvent
Achieve an event for a recipient
POST
/flows/{flowName}/:execute
Execute a named flow
PUT
/apps/register/{identifier}
Register a device for push
PUT
/apps/consent/{identifier}
Grant push notification consent
GET
/discovery/persondata
Discover person data fields
GET
/globaldata/tables/{tableName}
Get records from a global data table
POST
/recipients
Create a new recipient
PUT
/recipients/{recipientId}
Update or create a recipient
POST
/recipients/{recipientId}/events/{eventId}/:achieveEvent
Achieve an event for a recipient
POST
/flows/{flowName}/:execute
Execute a named flow
PUT
/apps/register/{identifier}
Register a device for push
PUT
/apps/consent/{identifier}
Grant push notification consent
GET
/discovery/persondata
Discover person data fields
GET
/globaldata/tables/{tableName}
Get records from a global data table
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Agillic bearer token sits in Jentic's vault. Each operation receives the token at execution time, so the agent's transcript and chain memory never carry the secret.
Intent-based discovery
Agents search by intent (e.g. 'execute an Agillic flow' or 'register a push device') and Jentic returns the matching operation with its input schema, including the path parameters and request body shape.
Time to first call
Direct integration: 1-2 days to wire bearer auth, recipient updates, and flow execution. Through Jentic: under an hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Agillic API through Jentic.
Why is there no official OpenAPI spec for Agillic API?
Agillic does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Agillic 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 Agillic API on agillic.net use?
This surface uses an HTTP bearer token in the Authorization header on every request. Jentic stores the token in its vault and injects it at execution time, so the credential never appears in agent context.
How do I execute a flow with the Agillic API?
Call POST /flows/{flowName}/:execute with the recipient ID and any context required by the flow. Useful for transactional sends like password resets where waiting for a scheduled segment would be too slow.
Can I register a device for push notifications through this API?
Yes. Use PUT /apps/register/{identifier} with the device token, then PUT /apps/consent/{identifier} to record consent. To remove a device, use DELETE /apps/consent/{identifier} followed by PUT /apps/unregister/{identifier}.
How do I update a recipient through Jentic?
Search Jentic for 'update an Agillic recipient'. Load the PUT /recipients/{recipientId} schema, populate the recipient ID and the fields to change, and execute. Jentic adds the bearer token before the call.
What are the rate limits for the Agillic API on agillic.net?
The OpenAPI spec does not declare explicit per-second limits. For larger jobs, prefer the export endpoints under /export to retrieve data in bulk rather than enumerating recipients.
GET STARTED