A2B Developer Playground
Reference and live request console for the A2B developer playground — the vendor and client halves of the marketplace API, driven by one credential pair.
Which token calls it
The API is split by side of the marketplace. Paste a token once and the console dims whichever half it cannot reach.
Identity
1 endpoints
Confirm which account a bearer token belongs to. The one call that takes the bearer token on its own.
Vendor
9 endpoints
What a supplier of respondents may read. Read-only by design — a vendor consumes what the client side set up.
Client
12 endpoints
What a company buying completes may read and write. Creating a project here is how the eight callback ids are minted.
Your first request
Every playground call carries both headers. The bearer token is the secret — its four-character prefix (clt_ or vnd_) says which table to resolve it in, so the row it matches is the caller. The X-Api-Token is the identity half, so a bearer token lifted on its own is not enough.
- Local
- http://localhost:8081
- Production
- https://dashboard.a2bsample.com
No handler anywhere takes a client id or a vendor id: the caller's id always comes from the token, and a project id in a path is ownership-checked rather than trusted.