Organization
The organization this credential is scoped to.
There is no way to name a different one. A credential describes exactly one organization, so an identifier in the path could only ever be your own or a refusal.
Authorization
BearerAuth org.readAuthorization: Bearer <key>, with a key from the console. Keys are
default-deny: each operation names the scope it needs, and an existing
key does not gain an operation until that scope is added to it.
In: header
Scope: org.read
Response Body
application/json
application/json
application/json
curl -X GET "https://internetdata.io/api/v1/iam/org"{
"rc": "string",
"org": {
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"name": "string",
"created": "2019-08-24T14:15:22Z"
}
}{
"rc": "string"
}{
"rc": "string"
}Identity GET
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.
Members GET
Read-only. Adding or removing a member is an invitation flow with email in the middle rather than a POST, and modelling it as one here would promise something this API does not do.