marketplace
GET /v1/marketplace/listings/{listing_id}/traffic-verification
The GA4 verified-traffic connection on your listing.
Authentication
Send an API key as a bearer token. This endpoint checks no specific permission, so any key for your organisation can call it.
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 GET https://api.zinndigital.com/v1/marketplace/listings/{listing_id}/traffic-verification \
-H "Authorization: Bearer zdk_live_…"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
Q287 (s1006, owner D41), docs/83 §1f. not_connected, awaiting_property (Google said yes, pick the property), active (figures on the listing) or needs_reconnect (Google no longer accepts the grant). Never the token: it lives in Vault.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
listing_id (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
status | string<not_connected, awaiting_property, active, needs_reconnect> | Yes | — |
provider | string | No | — |
property_id | string | No | — |
property_name | string | No | — |
matched_host | string | No | — |
last_error | string | No | The last refusal code |
traffic | MarketplaceVerifiedTraffic | No | — |
Errors this endpoint can return
401 · 404