Docs menu

MCP tool · Bridge

get_bridge_stats

The Bridge's Stats tab: each creative bridged from a Meta ad account, its Meta ad next to its TikTok and Snapchat copies, with their spend and results over the period (7-day click attribution everywhere), each platform in its own currency.

Read only Scope: read Pro and Scale plans Credits: Free*

What it does

The Bridge's Stats tab: each creative bridged from a Meta ad account (yours, and others' sent to accounts you hold too), newest first: its source ad on Meta next to its copies on TikTok and Snapchat over since → until (7-day click attribution on every platform). Per platform: status (ok, no_target = never bridged there, not_connected = that account is not connected to this Apogee account, error), the ads, inputs (raw sums) and kpis (spend, revenue, ROAS, CPM, CTR, CPC, cost per purchase, hook and hold rates…), each in its own ad account's currency: never add platforms together.

Parameters

  • source_ad_account_id string required

    The Meta ad account the ads were bridged from (act_…)

    Matches ^(act_)?\d{1,32}$

  • since string required

    First day, YYYY-MM-DD

    Matches ^\d{4}-\d{2}-\d{2}$

  • until string required

    Last day, YYYY-MM-DD

    Matches ^\d{4}-\d{2}-\d{2}$

Example

Your assistant calls it for you when you ask in your own words. What it sends (MCP tools/call, JSON-RPC 2.0):

tools/call
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_bridge_stats",
    "arguments": {
      "source_ad_account_id": "act_1234567890",
      "since": "2026-10-01",
      "until": "2026-10-21"
    }
  }
}

The same call over HTTP with an API key, for an MCP client of your own (an assistant that signs in sends its OAuth token instead):

curl
curl -X POST https://app.apogee.ad/mcp \
  -H "Authorization: Bearer $APOGEE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_bridge_stats","arguments":{"source_ad_account_id":"act_1234567890","since":"2026-10-01","until":"2026-10-21"}}}'

Access and cost

PlansPro and Scale.
Scoperead: a connection or an API key without it does not see this tool (scopes).
EffectReads only: nothing is changed, in Apogee or on the ad account.
CreditsFree up to the daily free reads (5,000 a day on Pro, 10,000 on Scale), then 1 credit per read. A call that fails costs nothing (credits).
Rate limit600 MCP requests per 15 minutes on Pro, 1,200 on Scale (rate limits).
Daily capCounts 1 unit toward the 2,000 units one API key or assistant connection can use in 24 hours.

In the REST API

The same thing for your own code, with an API key:

Bridge: Ads of one platform launched on another (Meta → TikTok or Snapchat, and back), or a Meta → Meta copy between two ad accounts. Prepared, shown in full, then run after your explicit yes; a plan runs once, within 24 hours.

Last updated on . The parameters, limits, credits and error codes of these pages are generated from the code of the Apogee API (contract 2026-10-06).

A question, something missing? Write to hello@apogee.ad.

Book a demo

Pick the time that suits you.

Open in a new tab

Loading the calendar…

Talk to Founder