Destinations / Connect destination

Connect destination

POST/v1/destinations

Connect Meta or GA4 directly with a token. This path is for those two only, Google Ads connects through a handoff. The credentials object differs per platform (Meta needs access_token + meta_pixel_id; GA4 needs measurement_id + api_secret).

Body parameters

destination_type

string · required

meta or google-analytics.

credentials

object · required

The token fields for that platform.

Response fields

string

A fixed type id, e.g. dest_google-ads. Not a random UUID.

integration

string

The platform slug, e.g. google-ads.

name

string

Display name, e.g. Google Ads.

connected

boolean

True once credentials are configured and validated.

connection_metadata

object

Non-secret details once connected, e.g. account or measurement ids.

POST/v1/destinations

curl https://app.converly.io/api/v1/destinations \
  -H "Authorization: Bearer sk_live_…" \
  -d '{
    "destination_type": "meta",
    "credentials": {
      "access_token": "EAABsb…",
      "meta_pixel_id": "1234567890"
    }
  }'

201 Created

{
  "id": "dest_meta",
  "integration": "meta",
  "connected": true
}