Reference & Lookup Data · Integration
Adyntel
Add Adyntel to your product for your customers, and give your AI agents governed access to it.
Adyntel exposes one POST endpoint per ad library, so /facebook, /google, /linkedin and /tiktok are separate calls rather than a single search with a platform parameter, and a GET against any of them is rejected. Credentials are unusual: both api_key and email go in the JSON body, not in an Authorization header, and omitting either returns a field validation error rather than a 401. Most endpoints take a company domain or a Facebook page as the input and return the ads that library is currently exposing, while the TikTok search endpoint works from a keyword instead. Billing is per successful call that returns data, so a domain with no public page costs nothing, which makes retry logic safe but makes broad domain sweeps expensive quickly. fastn keeps each customer's Adyntel key and account email out of your codebase and maintains the connection as keys are rotated.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Adyntel key so competitor ad pulls are metered against their credit balance
Show a customer which ads a competitor domain is currently running on Meta and Google inside your dashboard
Track a watchlist of competitor domains and record when new creative appears in a library
Enrich an account record with the ad platforms a prospect is actively advertising on
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent look up the live ads for a named competitor domain and summarise the messaging themes
Have an agent run a TikTok keyword search and report which advertisers are bidding on a topic
Audit per tenant how many Adyntel lookups an agent made, since each successful call spends that tenant's credits
Example prompt
What Meta ads is this competitor domain running right now?
Set up Adyntel in 4 steps
- 01Enable the Adyntel connector from your fastn dashboard.
- 02Have each customer authorise their own Adyntel 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 Adyntel integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Adyntel integration without building it. Your customers connect their own Adyntel 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 Adyntel update is not your on-call problem.
- One integration serves your product and your agents. The same governed Adyntel 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 Adyntel, across other categories.
Salesforce
HubSpot
Notion
SnowflakeAdyntel integration FAQ
How do I add an Adyntel integration to my product?
Enable the Adyntel connector in your fastn dashboard, then let each customer authenticate their own Adyntel account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Adyntel client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Adyntel account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Adyntel 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 Adyntel 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 look up the live ads for a named competitor domain and summarise the messaging themes
Who maintains the Adyntel integration?
fastn does. When Adyntel 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 Adyntel 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 Adyntel results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Adyntel 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 Adyntel integration?
A common starting point: let a customer connect their own Adyntel key so competitor ad pulls are metered against their credit balance. 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 Adyntel integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Adyntel does not change your per-connector cost. You can start free with 3 connected accounts.
Add Adyntel to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.