Add Permissions to a Role

Widens a role: everyone who already holds it — directly, or through a group — can do the added things.

{id} is the role’s name, a slug such as midaz-editor; each entry in permissions is a permission id. There is no separate step to push the change out to holders; the role IS the grant.

Adding a permission the role already carries is not an error, so a partially applied form can safely be submitted again. On success the response has no body (204).

Failures:

• 400 — permissions is missing or empty.
• 404 — one of the permissions does not exist.
• 503 IDE-0066 — the identity provider is unavailable (unreachable, too slow to answer, or failing). Nothing about the request was wrong; retry it later.

POST /v1/roles/{id}/permissions

Add Permissions to a Role

cURL

curl --request POST \
  --url https://identity.sandbox.lerian.net/v1/roles/{id}/permissions \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "permissions": [
    "<string>"
  ]
}
'

400

{
  "code": "<string>",
  "entityType": "<string>",
  "err": "<unknown>",
  "message": "<string>",
  "title": "<string>"
}

Authorizations

Authorization · string · header · required

JWT bearer token issued by the identity provider.

Path Parameters

id · string · required

Role ID.

Example:

"midaz-editor"

Body

application/json

The permissions to add to the role.

permissions · string[] · required

Permission identifiers.

Minimum array length: 1

Response

204

No Content