Reference & Lookup Data · Integration
AeroLeads
Add AeroLeads to your product for your customers, and give your AI agents governed access to it.
AeroLeads is queried over plain GET requests to https://aeroleads.com/apis/details with first_name, last_name, company_url and api_key all passed as query string parameters, which means the key travels in the URL and will end up in any proxy or access log you put in front of it. A bad key returns HTTP 401 with the bare text "Wrong API key." rather than a JSON error object, so error handling written against a JSON parser breaks on the first failure. A second endpoint takes a LinkedIn profile URL and returns the person's name, job title, current and previous company, education and skills. The key itself is found under Settings then the API tab in the AeroLeads account, and lookups draw down that account's credit balance. fastn holds each customer's key server side so it never reaches a browser, and keeps the connection alive as keys change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own AeroLeads account so prospect lookups are charged to their credits and not yours
Fill in a missing work email on a lead record from the person's name and company domain
Expand a pasted LinkedIn profile URL into a structured contact record with title and employer
Run a verification pass over imported lists so contacts without a findable business email are flagged before outreach
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent find the business email for a named person at a named company and write it back to the CRM record
Have an agent enrich a batch of new signups with job title and employer before routing them to sales
Audit per tenant which lookups an agent ran, so credit consumption can be traced to the account that triggered it
Example prompt
Find the work email for this person at this company domain.
Set up AeroLeads in 4 steps
- 01Enable the AeroLeads connector from your fastn dashboard.
- 02Have each customer authorise their own AeroLeads account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the AeroLeads integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an AeroLeads integration without building it. Your customers connect their own AeroLeads account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an AeroLeads update is not your on-call problem.
- One integration serves your product and your agents. The same governed AeroLeads connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
APIVoidOften used alongside
Tools the same teams tend to run next to AeroLeads, across other categories.
Salesforce
HubSpot
Notion
SnowflakeAeroLeads integration FAQ
How do I add an AeroLeads integration to my product?
Enable the AeroLeads connector in your fastn dashboard, then let each customer authenticate their own AeroLeads account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no AeroLeads client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own AeroLeads account?
Yes. Every connection is scoped to the individual customer, so each authorises their own AeroLeads account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this AeroLeads integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent find the business email for a named person at a named company and write it back to the CRM record
Who maintains the AeroLeads integration?
fastn does. When AeroLeads changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does an AeroLeads lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should AeroLeads results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. AeroLeads is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the AeroLeads integration?
A common starting point: let a customer connect their own AeroLeads account so prospect lookups are charged to their credits and not yours. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the AeroLeads integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding AeroLeads does not change your per-connector cost. You can start free with 3 connected accounts.
Add AeroLeads to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.