TL;DR: The Meta Ads API, officially the Marketing API, is the door through which software reads and changes an ad account: campaigns, ad sets, ads, audiences, results. You do not call it yourself. Ads Manager, bulk uploaders, reporting dashboards and AI assistants call it for you, after you grant them access to your account. What you choose is the tool. The questions worth asking are about the tool: what it can touch, whether Meta approved it, and whether it holds your tokens or asks you for one.
What the Meta Ads API is
Meta's developer documentation calls it the Marketing API and describes it as the way to "automate advertising across Meta technologies". Through it a program can create campaigns, ad sets and ads, update, pause or delete them, and read "detailed insights and analytics" on how they perform. It covers Facebook, Instagram, Messenger and ads in WhatsApp Status.
The API works on the same objects you see in Ads Manager, in the same order. A campaign holds the goal. An ad set holds the budget, the schedule, the bidding and the audience. An ad holds the creative: the image or video, the text, the link. Meta's own table puts it this way:
| Setting | Campaign | Ad set | Ad |
|---|---|---|---|
| Goal | Yes | ||
| Schedule | Yes | ||
| Budget | Yes | ||
| Bidding | Yes | ||
| Audience | Yes | ||
| Creative | Yes |
Ads Manager is one program that uses this API. Every other tool that touches your account uses the same one. No second door exists.
Who calls it, and who does not
Nobody who runs ads types API calls. A developer writes software that does, and the advertiser uses the software. The line that matters is which software.
- Ads Manager and Business Suite. Meta's own interfaces. They cover everything, one ad at a time.
- Bulk tools. Spreadsheets or sheet-like screens that create many ads in one go through the API. The three ways to bulk upload Facebook ads compares them.
- Reporting dashboards. They read insights through the API and draw them for you.
- AI assistants. Claude, ChatGPT or Perplexity connected to an ad account through a Meta Ads MCP server, which turns your sentence into API calls and the answer back into a sentence.
- Your own script. Possible, with a developer, a Meta app and the access process below. Worth it when no tool does what you need.
The first four need nothing from you except permission. That permission is the subject of the next section.
What Meta asks of the software
Any program that calls the Marketing API runs inside a Meta app, registered in Meta's developer portal. Meta's authorization page sets out what such an app needs.
Permissions. An app that reads reports asks for the permission called ads_read. An app that creates or changes anything asks for ads_management. When a tool asks you to connect your Meta account, the screen that lists these permissions is the API asking on the tool's behalf. Meta's page: "Your app gets access when they click Allow."
An access tier. Every new app starts in what Meta now calls Limited access: "heavily rate-limited per ad account", "for development only", "not for production apps running for live advertisers". To serve real advertisers, the app has to pass Meta's App Review and reach Full access. Meta lists two conditions for that: at least 500 successful API calls in the past 15 days, and an error rate under 15 percent over the last 500 calls. The same page, updated May 5, 2026, announces the new names. Standard became Limited, Advanced became Full, and the call threshold went down from 1,500 to 500.
An access token. Once you click Allow, Meta gives the app a token tied to your account. Everything the app does afterwards travels with that token. Who holds it, and how, is the single most useful question to ask about a tool.
A version. Meta publishes a new API version two or three times a year and retires old ones. On the versions page, Marketing API v24.0 came out on October 8, 2025 and expires on October 6, 2026; v25.0 came out on February 18, 2026. A tool that stays on a retired version stops working. The tool's maker handles this, not you.
What to check in a tool before you connect it
Five questions, each answered by the tool's website or its connection screen:
- Which permission does it ask for? A reporting tool that asks for ads_management wants more than it needs. A tool that creates ads has to ask for it.
- Does it ask you for a token or an app? A finished product connects with one Allow click. If the setup tells you to create a Meta app, generate a token and paste it somewhere, the tool hands you the developer's work. The token then sits where you pasted it, in plain text.
- Where does the token live afterwards? On the tool's server, encrypted, or inside a chat window or a configuration file on your laptop?
- What happens before a write? The API itself has no undo. A campaign created with status ACTIVE spends money from the moment Meta approves it. A tool that shows you a preview before each write, and lets you choose whether new ads start paused or active, puts a step between a mistake and your budget.
- Can you see what it did? Meta records account activity, and some tools keep their own log of every change they made. Either way, you should be able to read back what the software did in your name.
Adsap answers those five like this. It asks for ads_management because it creates ads. You connect Meta once, in the Adsap web app, with the Allow click; an assistant then signs in to Adsap, with no app and no token to paste. The token stays on Adsap's server. Every write shows a preview first, and the audit log keeps each change. Whether new campaigns, ad sets and ads start paused or active is a setting you choose.
When you do need a developer
Three cases justify writing your own code against the Marketing API:
- A workflow no tool offers, such as rules that read data from your own systems before changing a budget.
- Volumes beyond what tools allow, such as thousands of ad changes a day across many accounts.
- A product of your own that other advertisers will use. Then the App Review, the access tier and the version calendar above are your job.
For everyone else, the API is already in the tools. The choice is which tool, and the five questions above are the checklist.
Frequently asked questions
Yes. Marketing API is Meta's name for it. Facebook Ads API and Meta Ads API are the names advertisers use. It is one API, part of Meta's Graph API, covering Facebook, Instagram, Messenger and WhatsApp Status ads.
Yes. Meta charges nothing for API calls. You pay for the ads you run and, if you use one, for the tool that calls the API for you.
No. A finished tool has its own Meta app, approved by Meta, and you connect to it with one Allow click. Creating an app and generating a token is only needed when you write your own code, or when a tool has skipped that work and passes it to you.
Mostly the other way round. Ads Manager uses the same API and sometimes gets features before the public API does, and some settings exist only in the interface. The API's advantage is scale and repetition: hundreds of ads from one sheet, or a question answered by an assistant in one sentence.
On Meta's versions page, read on October 27, 2026, Marketing API v25.0 is the latest listed, released February 18, 2026, and v24.0 expires on October 6, 2026. Tools move to new versions on your behalf.
Sources
All pages read on October 27, 2026.
- Meta for Developers, Marketing API overview, updated June 24, 2026: what the API does, the campaign, ad set and ad structure, the settings table and the WhatsApp Status note.
- Meta for Developers, Marketing API authorization, updated May 5, 2026: the ads_read and ads_management permissions, the Limited and Full access tiers, their conditions, the rename and the new threshold.
- Meta for Developers, Graph API and Marketing API versions: the release and end dates.