Storyden
Roles

Role Update Order

Update the global ordering of custom roles. The request body must include every non-default role identifier exactly once in the desired order of precedence.

Update the global ordering of custom roles. The request body must include every non-default role identifier exactly once in the desired order of precedence.

PATCH/roles/order

Authorization

storyden-session<token>

In: cookie

Request Body

application/json

role_ids*array<>

Ordered list of custom role identifiers in the desired sort order. Must include all custom roles exactly once without default roles.

Response Body

application/json

application/json

curl -X PATCH "https://loading/api/roles/order" \  -H "Content-Type: application/json" \  -d '{    "role_ids": [      "cc5lnd2s1s4652adtu50"    ]  }'
{
  "roles": [
    {
      "id": "cc5lnd2s1s4652adtu50",
      "createdAt": "2019-08-24T14:15:22Z",
      "updatedAt": "2019-08-24T14:15:22Z",
      "deletedAt": "2019-08-24T14:15:22Z",
      "misc": {},
      "name": "string",
      "colour": "string",
      "permissions": [
        "CREATE_POST"
      ],
      "meta": {}
    }
  ]
}
Empty
Empty
{
  "error": "string",
  "message": "string",
  "suggested": "string",
  "metadata": {}
}
Edit on GitHub

Role Update PATCH

Updates a role's attributes.

Access Key Create POST

Create a new access key for the authenticated account. Access keys are used to authenticate API requests on behalf of the account in a more granular and service-friendly way than a session cookie. Access keys share the same roles and permissions as the owning account and only provide a way to use an `Authorization` header as an way of interacting with the Storyden API. Access keys also allow an expiry date to be set to limit how long a key can be used to authenticate against the API.