prepare_bridge_transfer

What it does

Parameters

• source object required

  Where the ads come from: one of ad_ids, adset_ids, campaign_ids

  Fields (5)

  • platform string required

    One of meta, tiktok, snapchat

  • ad_account_id string required

    The ad account (list_ad_accounts): Meta act_…, a TikTok advertiser id, a Snapchat ad account id

    Matches ^(act_\d{1,32}|[A-Za-z0-9][A-Za-z0-9-]{0,63})$

  • ad_ids array of strings optional

    The ads to transfer (cross-platform: 50 max per run)

    1 to 100 items

    Matches ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$

  • adset_ids array of strings optional

    Meta: ad sets (cross-platform: their ads; Meta → Meta: the ad sets themselves, 20 max)

    1 to 20 items

    Matches ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$

  • campaign_ids array of strings optional

    Meta: campaigns (cross-platform: their ads; Meta → Meta: the campaigns themselves, 5 max)

    1 to 5 items

    Matches ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$

• destination object required
  Fields (5)

  • platform string required

    One of meta, tiktok, snapchat

  • ad_account_id string required

    The ad account (list_ad_accounts): Meta act_…, a TikTok advertiser id, a Snapchat ad account id

    Matches ^(act_\d{1,32}|[A-Za-z0-9][A-Za-z0-9-]{0,63})$

  • campaign_id string optional

    Required, except for a Meta → Meta copy of campaigns

    Matches ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$

  • adset_id string optional

    An existing destination ad set / TikTok ad group / Snapchat ad squad (list_adsets)

    Matches ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$

  • new_adset object optional

    Cross-platform: a new ad set copied from a template, instead of adset_id

    Fields (3)

    • template_adset_id string required

      An ad set / ad group / ad squad of the destination campaign whose settings the new one copies

      Matches ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$

    • name string required

      1 to 255 characters

    • daily_budget number optional

      Account currency; not for a TikTok CBO campaign

      > 0

• launch_status string optional

  Cross-platform. Default CREATED_PAUSED; SCHEDULED_* only with new_adset (+ schedule)

  One of CREATED_PAUSED, LIVE_NOW, SCHEDULED_PAUSED, SCHEDULED_LIVE

• schedule object optional

  A new ad set's schedule, in the destination account's time zone

  Fields (4)

  • date string required

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

  • time string required

    Matches ^\d{2}:\d{2}$

  • end_date string optional

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

  • end_time string optional

    Matches ^\d{2}:\d{2}$

• extra_fields object optional

  What the plan asked for (recap.missing): the destination's identity / profile / page, URL, CTA, headline

  Fields (8)

  • identity_id string optional

    TikTok: the identity the ads run under

    Matches ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$

  • identity_type string optional

    TikTok: one of the brand's TikTok accounts, TT_USER or BC_AUTH_TT through its Business Center (TikTok refuses a custom identity on these ads)

    One of TT_USER, BC_AUTH_TT

  • identity_bc_id string optional

    TikTok BC_AUTH_TT: the Business Center

    Matches ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$

  • profile_id string optional

    Snapchat: the public profile

    Matches ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$

  • page_id string optional

    Meta: the Facebook page

    Matches ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$

  • website_url string optional

    up to 2,048 characters

  • call_to_action string optional

    up to 40 characters

  • headline string optional

    Snapchat: 34 characters

    up to 255 characters

• meta_texts map optional

  Destination Meta: each source ad's texts (by source ad id), instead of the ones the plan suggested (recap.meta_texts)

  Keys match ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$

  Each value: object

  Fields (3)

  • primary_text string optional

    up to 2,200 characters

  • headline string optional

    up to 255 characters

  • description string optional

    up to 255 characters

• options object optional

  Meta → Meta copy only

  Fields (3)

  • keep_social_proof boolean optional

    Default true: reuse the source post (likes, comments) when Meta allows it

  • status string optional

    After the copy: PAUSED (default), ACTIVE, or INHERIT (on only what is on in the source)

    One of PAUSED, ACTIVE, INHERIT

  • name_suffix string optional

    up to 100 characters

• mapping map optional

  Meta → Meta copy: values for the plan's fields (recap.fields: pixel, page, audience, budget…), by key

  Each value: string

Example

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "prepare_bridge_transfer",
    "arguments": {
      "source": {
        "platform": "meta",
        "ad_account_id": "act_1234567890",
        "ad_ids": [
          "120200000000000003"
        ]
      },
      "destination": {
        "platform": "tiktok",
        "ad_account_id": "7000000000000000001",
        "campaign_id": "1800000000000000001",
        "adset_id": "1800000000000000002"
      }
    }
  }
}

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 -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":"prepare_bridge_transfer","arguments":{"source":{"platform":"meta","ad_account_id":"act_1234567890","ad_ids":["120200000000000003"]},"destination":{"platform":"tiktok","ad_account_id":"7000000000000000001","campaign_id":"1800000000000000001","adset_id":"1800000000000000002"}}}}'

Access and cost

In the REST API

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

• Create bridge transfer: POST /bridge-transfers

Related tools

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.

• bridge_transfer: Runs a prepared transfer, once, after your explicit yes; the plan is checked again first. Answers with the outcome (completed, partial, failed…) within about 25 seconds, or running. A Meta → Meta copy reuses each ad's post (likes, comments) when Meta lets the destination use it, and copies it as a new post otherwise.
• bridge_transfer_status: Where a transfer is: running, completed, partial (with the failures), failed, not run, or unknown (check the destination before running it again).
• list_bridge_transfers: The ads already bridged from a source ad account, newest first, with where each one went.
• 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.
• get_bridge_daily_stats: The Bridge's Daily tab: day by day, per platform, the spend, revenue, ROAS, impressions, link clicks and purchases of every creative bridged from a Meta ad account (366 days at most). Platforms are never added up.