For Agents
Manage Instantly cold-email accounts, campaigns, and leads — pause and resume sender accounts, run campaigns, and import leads programmatically.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Instantly 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 | shStep 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.
What an agent can do with Instantly API.
Provision and configure Instantly sender accounts via POST /accounts and PATCH /accounts/{id}
Pause and resume warm-up or sending on individual accounts via /accounts/{id}/pause and /accounts/{id}/resume
Create outbound campaigns and update their step sequences via /campaigns
GET STARTED
Use for: I want to create a new Instantly cold-email campaign, Pause sending on an Instantly account that is showing deliverability issues, Import a CSV of leads into an existing Instantly campaign, Resume warm-up on an Instantly account after it cooled down
Not supported: Does not handle SMS, transactional email, or CRM contact records — use for cold-email account, campaign, and lead management only.
Jentic publishes the only available OpenAPI specification for Instantly API, keeping it validated and agent-ready. The Instantly v2 API gives outbound sales and growth teams programmatic control over cold-email infrastructure, including sender accounts, campaigns, leads, and email sends. Across 26 endpoints, the API covers account warm-up pause and resume, campaign creation, lead import, and reply tracking, so an automation can keep multi-account outbound running without UI clicks. Authentication is a single API key passed in the Authorization header, which makes embedding the API into existing workflows straightforward.
Import and update leads attached to campaigns through the /leads endpoints
Read sent and received emails to drive reply-handling automations through /emails
Remove or archive accounts that have been deprecated for sending
Patterns agents use Instantly API for, with concrete tasks.
★ Account Health Auto-Pause
Listen to deliverability signals from an external monitor and call POST /accounts/{id}/pause when bounce or spam-complaint thresholds are exceeded, then POST /accounts/{id}/resume once the account recovers. This prevents domain reputation damage without requiring an operator to log into the Instantly dashboard, and the small endpoint surface makes the integration achievable in a few hours.
When monitor flags an account, POST /accounts/{id}/pause; when health recovers, POST /accounts/{id}/resume.
Lead Import from CRM to Campaign
When a CRM tags a contact as 'outbound-ready', push the contact into the matching Instantly campaign via the /leads endpoints with full custom variables for personalisation. The integration removes the manual CSV upload step and keeps the campaign seeded with fresh leads as soon as they qualify in the CRM.
For each CRM contact tagged 'outbound-ready', call the Instantly create-lead operation with the campaign id, email, and merge fields.
Reply Routing into a Helpdesk
Poll /emails for inbound replies to outbound campaigns, classify intent, and forward qualified replies into a sales inbox or helpdesk. This avoids the trap of replies sitting unread in a sender mailbox by routing them to the system where reps actually work.
List Instantly emails received in the last hour, filter to replies, and create a corresponding helpdesk ticket for each one.
AI Agent Outbound Operator via Jentic
An AI agent given access to Instantly through Jentic can spin up a campaign, attach leads, and respond to deliverability alerts on its own. Jentic exposes each Instantly v2 operation by intent and isolates the API key in its vault, so the agent makes structured calls without seeing the credential.
Through Jentic, call instantly_create_campaign with a name and step sequence, then instantly_add_leads to attach a list of prospects to the new campaign.
26 endpoints — jentic publishes the only available openapi specification for instantly api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/accounts
Create a sender account
/accounts
List sender accounts
/accounts/{id}/pause
Pause an account
/accounts/{id}/resume
Resume an account
/campaigns
Create an outbound campaign
/accounts
Create a sender account
/accounts
List sender accounts
/accounts/{id}/pause
Pause an account
/accounts/{id}/resume
Resume an account
/campaigns
Create an outbound campaign
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Instantly API key is stored encrypted in the Jentic vault and injected into the Authorization header at execution time. Agents only ever see structured request and response data.
Intent-based discovery
Agents search Jentic by intent (for example 'pause an Instantly account' or 'create an Instantly campaign') and Jentic returns the matching v2 operation with its input schema.
Time to first call
Direct integration: 1-2 days to wire account, campaign, and lead endpoints with deliverability handling. Through Jentic: under 30 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Instantly API through Jentic.
Why is there no official OpenAPI spec for Instantly API?
Instantly does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Instantly 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 Instantly API use?
The Instantly API uses an API key sent in the Authorization header (the apiKey scheme is named 'apiKey' and bound to the Authorization header). Through Jentic, the API key sits in the encrypted Jentic vault and is injected into the request at execution time.
Can I pause and resume sender accounts with the API?
Yes. POST /accounts/{id}/pause stops sending and warm-up on a given account; POST /accounts/{id}/resume re-enables it. This is the recommended way to react to deliverability alerts without operator intervention.
What are the rate limits for the Instantly API?
The OpenAPI specification does not encode explicit rate limits. Treat each endpoint as a single-record operation, batch lead imports rather than firing one request per lead where possible, and back off on 429 responses returned by the gateway.
How do I create a campaign through Jentic?
Install with pip install jentic, then run the search-load-execute flow with the query 'create an Instantly campaign'. Jentic returns the operation backed by POST /campaigns; the agent supplies the campaign name, schedule, and step sequence and receives the new campaign id.
Can I read replies to my outbound campaigns?
Yes. The /emails endpoints expose sent and received messages for the connected accounts, so an automation can list inbound mail, filter to replies on a specific campaign, and forward them into a CRM or helpdesk.