Members
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.
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/members"{
"rc": "string"
}{
"rc": "string"
}{
"rc": "string"
}Organization GET
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.
List GET
Metadata only. A key's secret is never in a list - not here and not in the console - because a list is the response that ends up in logs, caches and support tickets. `retrievable` says whether the secret could still be read back at all. A key issued before this product stored secrets recoverably was never kept, so `reveal` will refuse it permanently; rotating produces one that can be read.