---
title: "Get a role"
method: GET
path: "/v1/roles/{role}"
tags: ["Roles"]
---

# Get a role

`GET /v1/roles/{role}`

## Request

- Base URL: `https://api.subscriby.net`
- URL: `https://api.subscriby.net/v1/roles/{role}`
- Auth: HTTP bearer

One role with its permission codes. `permissions` is a flat array of the exact ability strings granted by this role, the same strings used as token abilities, so you can match roles against tokens without a second round-trip.

## Path parameters

- `role` string, uuid, required

## Response `200`

The role resource with its permissions.

- object
  - `data` RoleResource, required: A role: the permission set one collaborator holds on a team. Every team seeds `admin`, `manager` and `viewer`, and creators add their own.
    - `id` string, required: The role's id.
    - `team_id` string, required: The team the role belongs to.
    - `code` string, required: The stable identifier permissions are addressed by, unique within the team and immutable after creation.
    - `name` string, nullable, required: The display name.
    - `description` string, nullable, required: What the role is for; null when none was given.
    - `owner_user_id` string, nullable, required: The user who created the role, the only one besides the team owner who may delete it.
    - `permissions` string[], required: The exact ability strings the role grants, the same strings used as token abilities, so roles can be matched against tokens without a second round-trip.
    - `created_at` string, nullable, required: When the role was created, ISO 8601.

## Other responses

- `401`: `AUTHENTICATION_REQUIRED`: the request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an `sbt_test_` token on production).
- `403`: `TOKEN_MISSING_ABILITY`: the token is valid but does not carry the ability this endpoint requires; `error.context.required_ability` names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers `FORBIDDEN`, `TEAM_TIER_REQUIRED` or `CONNECTOR_TIER_REQUIRED` with the same status, and says so in its own description.
- `404`: `RESOURCE_NOT_FOUND`: an id in the path names nothing the token can see. `TENANT_MISMATCH`: the project sits outside the token's `scope:project:` allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.
- `429`: `RATE_LIMITED`: the token has spent its 300 requests a minute or 10,000 an hour; `Retry-After` says when the next one is accepted.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)