Hanzo
OpenapiIam

Lists one kind of record in your organization — the older spelling of the… — GET /v1/iam/get-invitations

Lists one kind of record in your organization — the older spelling of the collection reads on the REST surface, over the same data and the same…

GET /v1/iam/get-invitations

Addresshttps://api.hanzo.ai/v1/iam/get-invitations
MethodGET
Operationget_iam_get-invitations
AuthAuthorization: Bearer $HANZO_API_KEY

Lists one kind of record in your organization — the older spelling of the collection reads on the REST surface, over the same data and the same permissions.

Secrets are stripped from every row. Send both a page number and a page size to page, and the total comes back alongside; send neither and you get the whole set. You see your own organization and no other, whatever the request asks for.

Scoping note (intentional, fail-closed): iam's ownership model is mixed — users/roles/permissions are owned by their tenant org, while organizations/ applications/providers/certs are platform-owned (Owner "admin"). A SuperAdmin (Scope → the requested owner, empty = all) therefore lists every entity, which is the console-admin path. A non-super is pinned by Scope to its own org, so it lists its tenant-owned entities correctly and is refused the platform-owned lists at the Guard (owner "" or "admin" both deny) — a safe 403, never another tenant's rows. Non-super, membership-scoped views of the platform-owned entities (e.g. an org console's own app list keyed on Application.Organization) are a separate, additive surface, not a silent behavior of this generic lister.

Request

GET /v1/iam/get-invitations takes no parameters and no body — the credential is the whole request.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo iam get-invitations

IAM API · All Hanzo APIs · Interactive reference

How is this guide?

On this page