Create a role

​

Body·

required
application/json

Fields accepted when creating a role. Unknown or read-only fields are rejected.

  • Active roles are assignable; inactive are retired.

  • The role grouping used for ordering and display (replaces the legacy Section). References teams.id.

Responses

  • application/json
  • application/json
  • application/json
  • application/json
  • application/json
Request Example for post/roles
curl https://api.weddingoperatingsystems.com/api/v1/roles \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{
  "label": null,
  "status": "inactive",
  "teamId": null,
  "order": null,
  "category": null
}'
{
  "data": {
    "id": "123e4567-e89b-12d3-a456-426614174000",
    "label": null,
    "status": "inactive",
    "teamId": null,
    "order": null,
    "category": null,
    "createdTime": "2026-09-30T06:22:05.745Z",
    "lastEditedTime": "2026-09-30T06:22:05.745Z"
  }
}