canonical: https://jentic.com/apis/aeroleads.com/aeroleads # AeroLeads API 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. ## For AI agents Look up business emails and phone numbers for named prospects, enrich existing contacts, and pull saved AeroLeads prospect lists. ## Scope Does not handle email sending, deliverability scoring, or sales-sequence orchestration - use for B2B contact discovery and enrichment lookups only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance and the agent only sees the structured prospect record returned by AeroLeads. Example prompt: 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 | 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 | ## Key resources - **Prospects** — Search and enrich individual prospect records via /search and /find - **Lists** — Retrieve saved lists and their prospect rows via /lists and /lists/{listId}/prospects ## Why Jentic - **Setup:** Wiring the AeroLeads API by hand means learning its api_key header and coding calls across its search, find, and list endpoints. Through Jentic you install once, import the AeroLeads API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** AeroLeads puts the list id in the URL path for list prospects (/lists/{listId}/prospects), while search and find take their input in the body, so a rule can pin the agent to reading one list or limit it to the lookup operations it needs. You choose which operations are in the allowed set, so anything you leave out is not reachable. - **Credential handling:** Your AeroLeads api_key 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 'find a business email by name', and Jentic returns the matching AeroLeads operation with its input schema so the agent picks search or find without browsing the reference docs. ## Related APIs - **Apollo.io** — Larger B2B database with sales engagement and sequencing built in - **Clearbit** — Company and person enrichment across firmographics and technographics - **Snov.io** — Email finder, verifier, and outbound sequencer in one platform - **Salesforce** — CRM destination for enriched prospect records ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the AeroLeads API? Yes. Because Jentic One is self-hosted, your own rules decide which AeroLeads operations the agent can reach, so you can grant only the lookup calls, POST /search and POST /find, and leave the list endpoints out of the allowed set. Since the list id sits in the URL path for GET /lists/{listId}/prospects, a rule can pin the agent to reading a single list rather than every saved list. Anything you do not add to the allowed set is not callable, and your api_key stays inside your own instance and is injected only at execution time.