AeroLeads API
★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey4 EndpointsREST
For Agents
Look up business emails and phone numbers for named prospects, enrich existing contacts, and pull saved AeroLeads prospect lists.
Use for: Find the business email for a named prospect at a target company, Get a phone number for a contact whose name and employer I already know, Search AeroLeads for a sales VP at a specific SaaS company, Enrich a list of prospects with verified email addresses
Not supported: Does not handle email sending, deliverability scoring, or sales-sequence orchestration — use for B2B contact discovery and enrichment lookups only.
Jentic publishes the only available OpenAPI specification for AeroLeads API, keeping it validated and agent-ready. AeroLeads is a B2B prospecting service that finds business email addresses, phone numbers, and contact records from LinkedIn and other public sources. The API exposes a /search endpoint to look up prospects by name and company, a /find endpoint to enrich a known contact with email and phone, and list endpoints to retrieve saved prospects. Authentication uses an api_key header issued from the AeroLeads dashboard.
Install Jentic One Beta
Connect the AeroLeads API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AeroLeads 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 AeroLeads API.
Search for a prospect's business email and phone number by full name and company
Enrich a known contact record with verified email and phone details
Retrieve every saved list in the AeroLeads account
Pull all prospects stored in a specific AeroLeads list
Feed enriched contact records into outbound sales sequences and CRM imports
Use Cases
Patterns agents use AeroLeads API for, with concrete tasks.
★ Outbound Sales Prospect Enrichment
Turn a list of names and companies into email and phone contact records ready for an outbound sequence. POST /search returns the AeroLeads prospect record for a single name+company pair, POST /find verifies and enriches an existing record, and the list endpoints export saved prospects in bulk. Sales-development teams can refresh segments without leaving their CRM or Sequence tool.
Call POST /search with first_name=Jane, last_name=Smith, and company=Acme Corp and return the verified email and phone number
CRM Contact Refresh
Keep CRM contact records current by re-enriching them through AeroLeads. POST /find takes a known contact and returns the latest email, phone, and source attribution. Combined with GET /lists/{listId}/prospects this supports a periodic refresh job that fixes stale CRM contacts and improves deliverability for marketing campaigns.
Pull every prospect from GET /lists/{listId}/prospects, then call POST /find on each to return refreshed email and phone fields
List-Based Outreach Workflow
Use AeroLeads lists as the source of truth for an outbound campaign. GET /lists returns every saved list and GET /lists/{listId}/prospects returns the prospect rows in one of them. The workflow becomes: build the list inside AeroLeads, then pull it via API into the email tool, marketing automation system, or BI dashboard.
Call GET /lists, pick the list named 'Q3 SaaS prospects', then GET /lists/{listId}/prospects and write the rows to a CSV
AI Agent Email Lookup
Give an AI agent the ability to answer 'what is X's email at company Y?' directly. Through Jentic, the agent searches by intent, loads the AeroLeads /search schema, and executes with the user's filters. The api_key stays in the Jentic vault and the agent only sees the structured prospect record returned by AeroLeads.
Search Jentic for 'find business email by name and company', load the /search schema, and execute with the prospect's name and company
Key Endpoints
4 endpoints — jentic publishes the only available openapi specification for aeroleads api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/search
Search for a prospect's email and phone by name and company
POST
/find
Enrich a known contact record with verified email and phone
GET
/lists
List all saved AeroLeads prospect lists
GET
/lists/{listId}/prospects
Retrieve every prospect saved in a list
POST
/search
Search for a prospect's email and phone by name and company
POST
/find
Enrich a known contact record with verified email and phone
GET
/lists
List all saved AeroLeads prospect lists
GET
/lists/{listId}/prospects
Retrieve every prospect saved in a list
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Your AeroLeads api_key is stored encrypted in the Jentic vault and injected as the api_key header at call time. Agents receive scoped execution rights and the raw key never enters their context.
Intent-based discovery
Agents search by intent (e.g. 'find business email by name') and Jentic returns the matching AeroLeads operation with its input schema, so the agent picks /search or /find correctly without browsing docs.
Time to first call
Direct AeroLeads integration: a few hours to wire auth, error handling, and the list-export flow. Through Jentic: under 15 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AeroLeads API through Jentic.
Why is there no official OpenAPI spec for AeroLeads API?
AeroLeads does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AeroLeads 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 AeroLeads API use?
AeroLeads uses an api_key passed in a header named api_key, obtained from your AeroLeads account dashboard. Through Jentic the key is stored encrypted in the vault and injected at execution time, so the agent's context never contains the raw secret.
Can I find a business email by name and company with the AeroLeads API?
Yes. POST /search accepts a first name, last name, and company and returns the prospect's business email and phone number when AeroLeads can verify them against its sources. Use POST /find to enrich a contact record you already have.
How do I export an AeroLeads list through the API?
Call GET /lists to retrieve the list IDs in your account, then GET /lists/{listId}/prospects to pull every prospect saved in that list. The response contains the same rows you see in the AeroLeads dashboard.
What are the rate limits for the AeroLeads API?
AeroLeads applies plan-tier credit limits rather than fixed per-second rates; specific allowances are not declared in the spec. Check your plan in the AeroLeads dashboard and watch for 429 responses, which Jentic surfaces verbatim.
How do I look up a prospect's email through Jentic?
Run pip install jentic, search Jentic with 'find business email by name and company', load the /search schema, and execute with first_name, last_name, and company. Jentic returns the parsed prospect record without exposing your api_key.
GET STARTED