ads

POST /v1/ads/connect/linkedin

LinkedIn's authorize URL to connect LinkedIn ad accounts (za-41).

All ads endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The key must carry the ads.manage permission; a key without it is refused with 403, not 404.

Where your organisation id goes

This endpoint takes org_id as a field in the JSON body.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/ads/connect/linkedin \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Gated on ads.manage. The same flow as Google's and Meta's, over LinkedIn OAuth 2 (scopes r_ads r_ads_reporting): the browser goes to authorize_url (www.linkedin.com/oauth/v2/authorization) and LinkedIn returns it to /v1/ads/connect/linkedin/callback, which sends it on to the dashboard's account picker (/ads?connect=pick&grant=<id>&platform=linkedin). LinkedIn is READ-ONLY in Zinn® Ads for now: campaigns and spend are read, nothing is changed (a write is refused readOnlyNetwork). Every refusal on the LinkedIn path carries the network-neutral code (netNotConfigured, netNoSuchGrant, netScopeNotGranted, …) whose words name LinkedIn Ads through {network}, never Google.

Request body

NameTypeRequiredWhat it is
org_idstringNo—

Response

NameTypeRequiredWhat it is
authorize_urlstringYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429