IAM API

IAM

The company’s IAM, for its admins: who may do what in its products, everyone’s API keys, and what was done. Giving a role takes a person signed in to Yet — with a key, it is refused — so a leaked key never hands out more than its person had.

Base URL https://acme.yet.com.br/api/settings

Settings answer at your company’s own address — acme here — and take a key of someone who runs them.

List access

GET/api/settings/iam/access

Every role given in Cloud — everywhere (*) or in one environment.

Who: Runs the company’s Settings

Request

curl https://acme.yet.com.br/api/settings/iam/access \
  -H "Authorization: Bearer $YET_API_KEY"

Response · 200

[
  {
    "email": "bruno@acme.dev",
    "environment": "*",
    "role": "developer",
    "granted_by": "ana@acme.dev",
    "granted_at": "2026-10-23T12:00:00Z"
  }
]

List everyone’s keys

GET/api/settings/iam/keys

Who holds a key, since when, last used when.

Who: Runs the company’s Settings

Request

curl https://acme.yet.com.br/api/settings/iam/keys \
  -H "Authorization: Bearer $YET_API_KEY"

Revoke anyone’s key

DELETE/api/settings/iam/keys/{id}

It stops working at once; its person can make another in their Preferences.

Who: Runs the company’s Settings

Request

curl -X DELETE https://acme.yet.com.br/api/settings/iam/keys/{id} \
  -H "Authorization: Bearer $YET_API_KEY"

Response · 200

{
  "ok": true
}

List activity

GET/api/settings/iam/activity

What was done, by whom, and from where — the apps, an SDK, Terraform — the latest first.

Who: Runs the company’s Settings

Request

curl https://acme.yet.com.br/api/settings/iam/activity \
  -H "Authorization: Bearer $YET_API_KEY"

Response · 200

[
  {
    "id": 412,
    "at": "2026-10-23T12:00:00Z",
    "actor": "ana@acme.dev",
    "via": "api-key",
    "action": "environment.create",
    "target": "staging",
    "detail": "staging.acme.dev"
  }
]