canonical: https://jentic.com/apis/7targets.ai/7targets

# 7Targets API

Jentic publishes the only available OpenAPI specification for 7Targets API, keeping it validated and agent-ready. The 7Targets API is the integration interface for 7Targets, an AI sales assistant that automates lead nurturing and follow-up email sequences. The four endpoints cover lead creation and updates, stopping follow-up sequences, and assigning leads to specific AI assistants inside an account. Sales and marketing teams use it to push new leads from forms or CRMs into the 7Targets nurture engine without manual entry. Authentication uses a bearer token issued in the 7Targets account settings.

## For AI agents

Push new leads into 7Targets to be nurtured by an AI sales assistant, stop follow-up sequences, and reassign leads between assistants inside the account.

## Scope

Does not handle email composition, deliverability monitoring, or conversation analytics - use only to push leads, stop follow-up, and reassign assistants inside an existing 7Targets account.

## Capabilities

- Push a new lead into 7Targets so the AI sales assistant begins follow-up
- Update an existing lead's contact information or status
- Stop the follow-up sequence on a lead that has converted or unsubscribed
- Assign a lead to a specific AI assistant inside the 7Targets account

## Use cases

### Auto-Enroll New Leads from a Web Form

Marketing teams push leads captured by web forms or webinars directly into 7Targets so the AI sales assistant starts nurture emails within minutes. The /leads endpoint accepts the contact details and assistant assignment in a single call, replacing manual CSV uploads or per-lead entry. Wiring a form to 7Targets typically takes a half-day for a single source.

Example prompt: Call POST /leads with the form submission's name, email, company, and assigned assistant ID, and confirm the response includes a lead ID.

### Stop Follow-Up When a Lead Replies

Sales operations teams listen for inbound replies in their email or CRM and call /leads/stop/followup to halt the AI assistant's nurture sequence as soon as the lead engages. This prevents over-messaging and is often wired through CRM webhooks. End-to-end automation is around half a day to set up.

Example prompt: When a CRM marks a lead as replied, call POST /leads/stop/followup with the 7Targets lead ID and confirm the assistant stops sending.

### Reassign Leads Between Assistants

Teams running multiple AI assistants - for example, one tuned for SMB and another for enterprise - use /leads/assistant to move leads to the right assistant after qualification. The endpoint accepts the lead ID and target assistant, replacing manual edits in the 7Targets dashboard. Setting up the reassignment rule typically takes a day.

Example prompt: After qualification, call POST /leads/assistant with the lead ID and the enterprise assistant ID and verify the lead is now nurtured by the enterprise sequence.

### AI Agent Outbound Coordination via Jentic

An AI agent connected through Jentic can read new leads from any source, push them into 7Targets, and stop follow-up when an inbound reply arrives - all in a single conversation. Jentic stores the bearer token in the vault and exposes the four 7Targets operations by intent. End-to-end response time per lead is a few seconds.

Example prompt: Search Jentic for 'add a lead to 7Targets', load POST /leads, and execute it for the new contact, then load /leads/stop/followup to halt the sequence when a reply is detected.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /leads | Create or update a lead |
| POST | /leads/stop/followup | Stop the follow-up sequence on a lead |
| POST | /leads/assistant | Assign a lead to a specific AI assistant |

## Key resources

- **Leads** — Create and update leads to be nurtured by the AI sales assistant
- **Follow-up Control** — Stop follow-up sequences when a lead converts or unsubscribes
- **Assistant Assignment** — Assign leads to specific AI assistants inside an account

## Why Jentic

- **Setup:** Wiring the 7Targets API by hand means managing its bearer token, targeting the api.7targets.com host, and shaping lead and assistant payloads yourself. Through Jentic you install once, import the 7Targets API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** 7Targets carries lead and assistant details in the request body rather than a resource id in the path, so limit the agent to the operations it needs, such as adding a lead, and leave out stopping follow-up or reassigning an assistant unless you add them. You choose the allowed set, so only the operations you pick can run.
- **Credential handling:** Your 7Targets bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add a lead to 7Targets' or 'stop follow-up for a lead', and Jentic returns the matching 7Targets operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Outreach API** — Sales engagement platform with sequences and human-led outreach
- **Salesloft API** — Sales engagement platform widely used for outbound cadences
- **Apollo.io API** — Prospecting database that supplies leads pushed into nurture sequences
- **HubSpot CRM Contacts API** — CRM that holds qualified contacts before AI nurture

## FAQ

### Why is there no official OpenAPI spec for 7Targets API?

7Targets publishes integration documentation in HTML form but does not distribute a machine-readable OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call 7Targets through structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the 7Targets API use?

The API uses HTTP bearer authentication. The token is generated in the 7Targets account settings and sent in the Authorization header. When called through Jentic the bearer token is held encrypted in the vault and attached at execution time, so it never appears in agent context.

### Can I push new leads into 7Targets from a web form with this API?

Yes. Call POST /leads with the contact's name, email, and any company or context fields, plus the assistant ID that should handle the lead. The 7Targets AI assistant begins follow-up emails on the configured cadence after the lead is created.

### What are the rate limits for the 7Targets API?

7Targets does not publish a numeric rate limit on its developer documentation. Treat the API as fair-use, batch lead pushes where possible, and back off on HTTP 429 responses. For nightly CRM sync, a single batched run of leads per assistant is preferable to a continuous push.

### How do I stop a 7Targets sequence when a lead replies through Jentic?

After running pip install jentic and setting JENTIC_AGENT_API_KEY, search Jentic for 'stop a 7Targets followup', load POST /leads/stop/followup, and execute it with the lead ID. Jentic injects the bearer token automatically and the AI assistant stops sending.

### Does the 7Targets API write the email content itself?

No. The API is an ingestion and control surface - it pushes leads in, halts sequences, and reassigns leads. The actual nurture emails are composed and sent by the 7Targets AI assistant configured inside the 7Targets dashboard, not via the API.

### Can I limit what my agent is allowed to do with the 7Targets API?

Yes. Because Jentic One is self-hosted, you decide which of the 7Targets operations your agent can call, and your own rules govern which credentials it may use. If an agent only needs to enroll new leads, you can allow POST /leads and leave out POST /leads/stop/followup and POST /leads/assistant, so it cannot halt sequences or reassign leads. Only the operations you pick are exposed to the agent, and the bearer token is attached at execution time rather than shared with it.