Resource roles
Operations of the Space Registry API. Paths are relative to your deployment's API host.
GET /api/space-registry-api/resource-roles
Every role DECLARED in this deployment
The roles a biome (or a system seed) has declared, each with what it is for and the space tiers a consumer resolves it at. Declaring a role and ANSWERING one are different questions: which resource plays a role is the organisation’s, per owner, and is served by /resource-role-bindings. An empty list is an answer — nothing has declared a role — never a defaulted catalogue.
Authentication: bearer token (Authorization: Bearer <token>)
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
resourceKind | query | string | no | Narrow to one kind, e.g. launch-definition — matched as the <kind>. prefix of the role key, the same narrowing the bindings list accepts. |
| Status | Description | Body |
|---|---|---|
| 200 | application/json ResourceRoleCatalogueResponseDtoDataEnvelope | |
| 400 | application/problem+json ProblemDetailsDto | |
| 401 | application/problem+json ProblemDetailsDto | |
| 403 | application/problem+json ProblemDetailsDto | |
| 404 | application/problem+json ProblemDetailsDto | |
| 409 | application/problem+json ProblemDetailsDto | |
| 422 | application/problem+json ProblemDetailsDto | |
| 500 | application/problem+json ProblemDetailsDto |