Whoami
The whoami operations of the v1 API.
GET
Try it: use a key with the least scope; requests go straight from your browser to the API. The key stays in this tab's memory and is gone on reload.
Describe the calling API key: its id, organization and scope.
Read-only and allowed for every scope, so automation can check that its key may write before it starts a change.
api_keyheader
AuthorizationBearer <alc_ API key>An A-Line.cloud API key, sent as Authorization: Bearer alc_.... Create keys in the dashboard; sessions are not accepted on /v1.
The calling key
application/json- response
The calling API key.
key_id?|The key's id.
Format
uuidscope*||tenant_id?|The organization the key acts on.
Format
uuidcurl 'https://api.a-line.cloud/v1/whoami' \ -H 'Authorization: Bearer alc_test_EXAMPLE_not_a_real_key'Example Response
{ "key_id": "1e779c8a-6786-4c89-b7c3-a6666f5fd6b5", "scope": "read", "tenant_id": "34f5c98e-f430-457b-a812-92637d0c6fd0"}