get/v2/me

Identify the calling tenant and key

Operation: getMe
Authentication: API key

The portal’s first call. Returns the tenant, the calling key’s scopes, and the scopes a key may be issued — so the UI can grey out what the caller cannot do instead of offering a button that returns 403.

Requires `keys:write`. It discloses the tenant’s plan, quota and revenue share, so it is not reachable with a check-only key — and specifically not with a publishable key, which sits in a public web page where anyone can read it.

Request

Responses

200The calling tenant and key.

tenantTenantrequired

keyobjectrequired

available_scopesstring[]required

400The request body or query failed validation.

errorobjectrequired

401No key, an unknown key, a revoked key, or a key whose tenant is not active. All four return an identical body on purpose: distinguishing them would let a caller discover which partners we have.

errorobjectrequired

403The key is valid but lacks the scope, or it asked for a scope it does not itself hold.

errorobjectrequired

404Not found, or not yours. A resource belonging to another tenant answers 404 rather than 403, because 403 would confirm the record exists.

errorobjectrequired

Example

curl

curl -X GET https://api.haavisa.com/v2/me \
  -H "Authorization: Bearer $HAAVISA_API_KEY"

More in Partner

Something unclear? The eligibility guide explains the model behind the answers; the errors guide covers the envelope.