/v1/auth/rolesCreate an authorization role
operation ID: post_v1_auth_roles
Overview
Create an authorization role. The authentication API establishes identity and manages the roles, grants, sessions, and service credentials used for authorization.
When to use it
- Use it when an application needs to create an authorization role.
- Use it when a client needs to sign in, inspect its identity, or an administrator needs to manage access.
Quick example
Set the base URL and replace generated identifiers or credentials with values from your installation.
cURL
curl --request POST \
--url "$ORDINATE_URL/v1/auth/roles" \
--header "Authorization: Bearer $ORDINATE_TOKEN" \
--header "Content-Type: application/json" \
--data '{
"name": "string",
"capabilities": [
"read"
]
}'Expected output · 201
Role created
Example 201 output
{
"role_id": "00000000-0000-4000-8000-000000000001",
"name": "string",
"capabilities": [
"read"
],
"system": false,
"valid_from_ns": 0,
"valid_to_ns": 0,
"tx_id": 0
}The cURL request sends the smallest contract-derived body and asks OrdinateDB to create an authorization role. The documented 201 response is role created.
How it works
OrdinateDB resolves a session or bearer credential to a principal, then evaluates roles, capabilities, and resource scope for each protected operation.
Reference
- Required capability
- admin
- Authorization scope
- handler-resolved target
Parameters
No parameters.
Request body
application/json
capabilitiesarrayrequiredarray
Capabilitystringvalues: read · annotate · enter · approve · amend · model-edit · registry-manage · calc-author · display-author · display-publish · episode-manage · redact · admin
namestringrequired
Example request body
{
"name": "string",
"capabilities": [
"read"
]
}Responses
201Role created
application/json
capabilitiesarrayrequiredarray
Capabilitystringvalues: read · annotate · enter · approve · amend · model-edit · registry-manage · calc-author · display-author · display-publish · episode-manage · redact · admin
namestringrequiredrole_idstringrequired- format: uuid
systembooleanrequiredtx_idintegerrequired- format: int64
valid_from_nsintegerrequiredUTC Unix timestamp in nanoseconds
format: int64valid_to_nsany ofrequiredany of
option 1
integerUTC Unix timestamp in nanoseconds
format: int64option 2
null
Example 201 output
{
"role_id": "00000000-0000-4000-8000-000000000001",
"name": "string",
"capabilities": [
"read"
],
"system": false,
"valid_from_ns": 0,
"valid_to_ns": 0,
"tx_id": 0
}400Invalid role
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 400 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}401Authentication required
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 401 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}403Required capability is not granted
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 403 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}409Role name already exists
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 409 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}503Model database is not configured
application/json
ErrorEnvelope
codestringrequiredcorrelation_idstringrequired- format: uuid
detailsobjectoptionalerrorstringrequired
Example 503 output
{
"error": "string",
"code": "account-sealed",
"correlation_id": "00000000-0000-4000-8000-000000000001"
}Code examples
These examples are generated from the source contract. Replace the base URL, credentials, identifiers, and minimal generated values for your instance.
JavaScript
const ordinateUrl = "http://localhost:8080";
const token = "<bearer-token>";
const response = await fetch(`${ordinateUrl}/v1/auth/roles`, {
method: "POST",
headers: {
Authorization: `Bearer ${token}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"name": "string",
"capabilities": [
"read"
]
})
});
if (!response.ok) {
throw new Error(`OrdinateDB returned ${response.status}: ${await response.text()}`);
}
const data = await response.json();
console.log(data);Related topics
- Authentication guide — Understand the prerequisite concepts and transport behavior for this operation.
- REST endpoint index — Find other operations in Authentication.