ads

POST /v1/ads/connections/{connection_id}/crm-sources/{vendor}/upload

Send one CSV file of leads or of calls (za-160).

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.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

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/connections/{connection_id}/crm-sources/{vendor}/upload \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "content": <string> }'

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; audit action ads.crm_upload. At most 5,000 rows / 5 MB per file (send any number of files). A lead at a mapped stage, and a call at least min_call_seconds long, become one outcome each, only with consent; the same file twice stores nothing twice. Stored outcomes are uploaded to the network by the outcome push.

Parameters

NameTypeRequiredWhat it is
connection_id (path)stringYes—
vendor (path)string<csv, calls_csv>Yes—

Request body

NameTypeRequiredWhat it is
contentstringYesThe CSV text, header row first.

Response

NameTypeRequiredWhat it is
dataAdsCrmSyncResultYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429