GET /v1/marketplace/listings/{listing_id}/reveal

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

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}/reveal \
  -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

docs/83 §3. The masking rule is "not signed in", and a crawler is never signed in — so this is a SEPARATE authenticated endpoint rather than a richer variant of the public page. A user-agent branch would be cloaking, and the penalty lands on the whole storefront. ⚠️ Today the gate is "signed in". M4 tightens it to "has bought" when orders exist; that is the honest state rather than the final one.

Parameters

Response

Errors this endpoint can return

401 · 404