← Back to blog

The AdCrunch REST API Is Live — Bring Your Ad Data Into Your Own Stack

AdCrunch now exposes a REST API alongside MCP. Authenticate with an org-owned API key from console settings and pipe live ad data into your dashboards, warehouse, or in-house tooling.

  • Product update
  • API
  • MCP
The AdCrunch REST API Is Live — Bring Your Ad Data Into Your Own Stack

AdCrunch is MCP-first. Your AI agent talks to your campaigns in plain language, no glue code required — that’s the headline feature, and it’s not changing.

But sometimes you don’t want a chat. You want code. You want yesterday’s spend in the dashboard your team already opens every morning, or campaign deltas piped into the BI tool your finance lead lives in, or a Slack bot that pings the channel when a budget threshold is crossed.

For that, you need a REST API. Starting today, AdCrunch has one.

What’s New

The AdCrunch REST API is now available, with the same live ad data your MCP endpoint surfaces — exposed as plain HTTP, ready for whatever you’re building.

To call it, you’ll need an API key. A new API Keys page lives under console settings, where any teammate in your org can:

  • Create a long-lived REST API key
  • List the keys currently active in the org
  • Revoke any key the moment a project ends or a teammate moves on

Keys are organization-owned, not user-owned. They survive offboarding. They don’t break when someone’s session expires. They belong to the team, not to the person who happened to click “Create” first.

What the API Unlocks

Authenticate any request with a standard bearer header:

Authorization: Bearer <your-api-key>

That gets you campaigns, ad groups, ads, and performance metrics across every platform connected to your account. Full reference at docs.adcrunch.dev/api.

When to Use the REST API vs. MCP

Both reach the same underlying data, scoped to the same organization. Pick by the shape of the integration:

  • Use MCP when an AI agent is the consumer — Claude, Cursor, ChatGPT, or your own. The OAuth flow handles auth without you minting anything by hand.
  • Use the REST API when code is the consumer — cron jobs, BI connectors, warehouse loaders, in-house dashboards, Slack bots. Anywhere a long-lived bearer token is the right primitive.

You can run both in parallel. They read the same live context.

How to Get Started

  1. Open the console and head to Settings → API Keys.
  2. Click Create key, name it after where it’ll live (warehouse-loader, slack-bot, weekly-report-cron), and copy the token. It’s shown once.
  3. Store it like any production secret. Use it as a Authorization: Bearer token against the endpoints documented at docs.adcrunch.dev/api.

No app registration. No quota application. Just a key.

AdCrunch still leads with MCP — that’s where the product is most differentiated, and that’s where your AI agent gets the most leverage. But your ad data shouldn’t be stuck behind any one interface, agent or otherwise. With a REST API and organization-owned keys, you can pipe live performance into whatever already runs your business.

Ready to plug AdCrunch into your own stack?

Connect Your Ad Accounts to AdCrunch → Free Early Access

Read the REST API docs →

First 100 teams get full access at no cost.

Chat on WhatsApp