7Targets API

Name: 7Targets API
Brand: 7Targets API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbearer4 EndpointsREST

For 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.

Install Jentic One Beta

Connect the 7Targets API to your agent

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

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

GET STARTED

Start building with 7Targets API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use 7Targets API for, with concrete tasks.

★ 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.

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.

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.

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.

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

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

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

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

Why Jentic?

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

Credential isolation

7Targets bearer tokens are stored encrypted in the Jentic vault (MAXsystem) and injected into the Authorization header at execution time. Agents receive scoped access — the raw token never enters the prompt or output.

Intent-based discovery

Agents search Jentic with intents like 'add a lead to 7Targets' or 'stop a 7Targets followup' and Jentic returns the matching operation with its input schema, so the agent calls the right endpoint without reading the integration docs.

Time to first call

Direct integration with the 7Targets API takes about half a day to wire a form-to-lead flow. Through Jentic the same call is reachable in under thirty minutes.

FAQs

Specific to using 7Targets API through Jentic.

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 at https://app.jentic.com/sign-up.

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.

7Targets API

Connect the 7Targets API to your agent

Capabilities

Start building with 7Targets API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs