/api/developer/me
The only call in this reference that does not need X-Api-Token — it is how a caller discovers what its api token is in the first place.
The console's Verify button posts this call with the bearer token alone, then compares the apiToken it answers with against what is typed into the X-Api-Token box. That is what turns the header chip into vendor · Acme Panel · api token ✓.
The exact envelope is owned by the backend, so the console reads type, name and apiToken leniently — a nested caller object works just as well as the flat shape documented here.
https://dashboard.a2bsample.com/api/developer/meAuthorizationas a header./api/developer/mehttps://dashboard.a2bsample.com/api/developer/meSend a request to see the response.
Example request
Request
Headers2
AuthorizationstringrequiredThe secret half of the credential pair. Bearer clt_… for a client caller, Bearer vnd_… for a vendor caller — the four-character prefix says which table to resolve it in, so the row it matches is the caller. DeveloperApiAuthFilter resolves it before any handler runs.
AcceptstringoptionalResponse media type.
Responses
The account this bearer token resolves to.
successboolean- Whether the call succeeded.
typestring- Which side of the marketplace this token calls from. Decided by the token prefix, not by anything the caller sends.
idstring<uuid>- The caller's own id. Never accepted as a parameter anywhere — every handler takes it from the token.
namestring- Company name, for display.
apiTokenstring- The identity half of the pair — 40 hex characters. This is the value that has to arrive as
X-Api-Tokenon every other call.