GET /v1/marketplace/listing-types

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/listing-types \
  -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

What populates the chooser on the seller's "start a listing" form. Requires an **approved** Zinner® — the same gate `createMarketplaceListing` applies, so the chooser and the create call can never disagree about who may sell. ⛔ Excludes archived types, types with no vertical, and `first_party_only` types (docs/78 §6 ruling 7 — those skip review and carry no commission row, so offering one to a third party would publish straight to the storefront with no queue). `createMarketplaceListing` already refuses them with `FIRST_PARTY_ONLY`, and a chooser that offers a choice the next call rejects is the #2872 defect in another costume. ⭐ This endpoint existed nowhere until #2606. The only list of listing types was `/v1/admin/marketplace/listing-types`, which a vendor cannot call — so the seller form had no way to populate a picker, and the create control was simply never built. Measured in a browser on 2026-08-19 as an approved vendor: `/sell` rendered its heading and "You have not listed anything yet." with **no button, link or input** on the page.

Response

Errors this endpoint can return

401 · 404 · 422