Identity

Server URLloading...

GET

/api/v1/iam/identity

Send

Authorization

The identity behind this credential: what it is, the organization it is scoped to, and the scopes it currently holds.

user is present for an OAuth token and ABSENT for an API key, which has an organization but no person behind it. credential.kind says which you are holding, so a client can branch without guessing from a missing field.

Narrower than what the console shows its own user on purpose: an integration needs a name to display and an organization to address, not a profile. The scopes array is what the credential may do RIGHT NOW, so a client can render its own capabilities rather than discovering them from a 403.

Response Body

curl -X GET "https://api.vpndetection.io/api/v1/iam/identity"

{
  "rc": "SUCCESS",
  "user": {
    "id": "3d86d1ef-f70b-4063-a3b8-f69605a8fc57",
    "fullname": "Ada Lovelace",
    "email": "ada@example.com"
  },
  "org": {
    "id": "7b309476-0e70-4225-9a46-5e25650094dd"
  },
  "scopes": [
    "account.read",
    "apikeys.read"
  ]
}

{
  "rc": "string"
}

{
  "rc": "string"
}