Lead API

Name: Lead API API
Brand: Lead API
Availability: InStock

✓ Official Vendor SpecCRMContact ManagementapiKey5 EndpointsREST

For Agents

Create, list, update, and delete sales leads across Salesforce, HubSpot, Pipedrive, Zoho, and other CRMs through one unified API.

Connect the Lead API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Lead API API.

Create a lead with name, company, email, phone, and source attribution via POST /lead/leads

List existing leads with cursor-based pagination through GET /lead/leads

Look up a single lead by ID to inspect its current state and ownership

Update a lead's owner, status, or custom fields with PATCH /lead/leads/{id}

GET STARTED

Start building with Lead API API

Explore with Jentic

View OpenAPI Document

The Apideck Lead API is a focused unified interface for working with sales leads across CRMs and lead-capture tools including Salesforce, HubSpot, Pipedrive, and Zoho. Five endpoints cover the full CRUD lifecycle on a single normalised lead resource — list, create, get, update, and delete — so a marketing form, chat widget, or AI agent can push qualified leads into whichever CRM the customer uses without per-vendor code. Authentication uses the standard Apideck Authorization header alongside x-apideck-app-id and x-apideck-consumer-id.

Use Cases

Patterns agents use Lead API API for, with concrete tasks.

★ Form-to-CRM Lead Capture

Wire a marketing form, chat widget, or event sign-up to push leads into whichever CRM the customer has connected (Salesforce, HubSpot, Pipedrive, Zoho). POST /lead/leads accepts the same payload across providers and returns the resulting lead ID, so the integration is one HTTP call regardless of CRM. Useful for SaaS products that don't want to build five CRM integrations.

Create a lead with name 'Jane Doe', company 'Acme Corp', email 'jane@acme.com', source 'demo-request' in the connected CRM and return the resulting lead_id

Lead Status Sync

Keep an external sales tool's lead status in sync with the customer's CRM. GET /lead/leads/{id} retrieves current state, PATCH /lead/leads/{id} updates owner or status, and a polling or event-driven loop reconciles changes. Works the same against any of the supported CRMs because Apideck normalises the lead schema.

For lead_id 'lead_42', PATCH the status to 'qualified' and assign owner_id 'user_77', then verify with GET /lead/leads/lead_42

Duplicate Lead Cleanup

Deduplicate inbound leads before they hit the sales team. List leads with GET /lead/leads, group by email or company domain, and delete duplicates with DELETE /lead/leads/{id}. The 5-endpoint surface keeps the cleanup script small and portable across CRMs.

List all leads, group by email, and for each group with more than one lead delete every lead except the most recently created

AI Agent Lead Capture via Jentic

An AI sales agent qualifies a website visitor in chat and files them as a lead. Through Jentic, the agent searches 'create a lead', loads the POST /lead/leads operation, and executes it with the captured details. Jentic stores the Apideck Authorization, x-apideck-app-id, and x-apideck-consumer-id headers separately so the agent never sees the raw key.

Through Jentic, search 'create a lead', load POST /lead/leads, and create a lead from the chat transcript with name, company, email, and a description summarising the conversation

Key Endpoints

5 endpoints — the apideck lead api is a focused unified interface for working with sales leads across crms and lead-capture tools including salesforce, hubspot, pipedrive, and zoho.

METHOD

PATH

DESCRIPTION

GET

/lead/leads

List leads

POST

/lead/leads

Create a lead

GET

/lead/leads/{id}

Get a lead by ID

PATCH

/lead/leads/{id}

Update a lead

DELETE

/lead/leads/{id}

Delete a lead

GET

/lead/leads

List leads

POST

/lead/leads

Create a lead

GET

/lead/leads/{id}

Get a lead by ID

PATCH

/lead/leads/{id}

Update a lead

DELETE

/lead/leads/{id}

Delete a lead

Why though Jentic?

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

Credential isolation

Apideck application keys, x-apideck-app-id, and x-apideck-consumer-id values are stored encrypted in the Jentic vault. Agents receive scoped execution tokens and never see the raw Authorization value, even when capturing leads on behalf of an end user.

Intent-based discovery

Agents search by intent (for example 'create a lead' or 'list new leads') and Jentic returns the matching Lead operation with its input schema, so the agent calls POST /lead/leads without consulting Apideck or CRM docs.

Time to first call

Direct Apideck Lead integration: half a day to a day to wire auth and pagination. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

HubSpot API

HubSpot-only direct API with deeper marketing-event and workflow features the unified Lead API does not surface.

Choose HubSpot direct when the customer is HubSpot-only and needs marketing automation features; choose Apideck Lead for write-once cross-CRM capture.

Alternative

Pipedrive API

Pipedrive-only API with native Pipedrive lead and deal stages.

Choose Pipedrive direct when the customer is Pipedrive-only and needs Pipedrive-specific deal pipeline features; choose Apideck Lead for portability.

Complementary

Apideck Vault API

Vault sets up the CRM connection and stores the OAuth tokens the Lead API executes against.

Use Vault first to authorise the customer's CRM connection; then call POST /lead/leads scoped to that consumer.

FAQs

Specific to using Lead API API through Jentic.

What authentication does the Apideck Lead API use?

An apiKey scheme on the `Authorization` header with your Apideck application key, plus `x-apideck-app-id` and `x-apideck-consumer-id` headers. Through Jentic these are stored encrypted in the vault and injected at execution; the agent only ever holds a scoped token.

Can I push a lead into Salesforce, HubSpot, and Pipedrive with the same call?

Yes. POST /lead/leads uses the same request shape regardless of the underlying CRM. The actual provider is determined by the connection associated with the x-apideck-consumer-id; provider-specific custom fields can be passed through Apideck's custom fields mechanism.

What are the rate limits for the Apideck Lead API?

The OpenAPI spec does not publish per-endpoint rate limits. Apideck applies plan-based limits at unify.apideck.com plus per-connector limits passed through from the underlying CRM (Salesforce's per-org daily limit, HubSpot's burst limits, etc.). See https://developers.apideck.com for current numbers.

How do I create a lead through Jentic?

Install with `pip install jentic`, then run the search query 'create a lead'. Jentic returns POST /lead/leads — load its schema, supply name, company, email, and any source attribution, then execute. The lead lands in whichever CRM the consumer has connected.

Does the Lead API support custom fields from my CRM?

Yes — Apideck Unified APIs accept custom fields on the lead payload that pass through to the underlying CRM. Use the Vault API's custom-mappings endpoints to map your custom field IDs to the connector's native field IDs before sending the lead.

Can I convert a lead to an opportunity through this API?

No. The Lead API covers lead CRUD only; conversion to opportunities, accounts, or contacts is handled by the Apideck CRM Unified API. After creating or updating a lead here, switch to apideck.com/crm for downstream pipeline operations.