User permission options

Request#

GET /api/v1/users/options

Requires users:permissions. See token permissions. The token creator must remain an active administrator of the token’s organization.

Send Authorization: Bearer YOUR_API_TOKEN and Accept: application/json.

Query parameters#

This endpoint does not use query parameters.

Example#

Set ASSETCENTER_API_TOKEN as described in the quick start. Replace example IDs with values from your organization.

curl --request GET "https://my.assetcenter.app/api/v1/users/options" \
  --header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
  --header "Accept: application/json"

Response#

200 OK. Illustrative response; IDs and values will differ.

{
  "data": {
    "permissions": [
      "can_create_assets",
      "can_create_subscriptions",
      "can_create_people",
      "can_create_locations",
      "can_bulk_import",
      "can_manage_asset_categories",
      "can_manage_subscription_categories",
      "can_manage_asset_events"
    ],
    "categories": [
      {
        "id": 7,
        "name": "Equipment",
        "type": "asset"
      }
    ]
  }
}

Behavior and constraints#

Returns all supported member permission names and the organization’s categories, ordered by ID. Each category has id, name, and type (asset or subscription). This response is not paginated. Use the corresponding category type in permission updates.

Errors#

401 means the customer bearer token is missing, expired, revoked, or invalid. 403 means the token lacks the required permission or its creator is no longer an active administrator. 404 means the requested member or invitation is unavailable in this organization. 422 identifies invalid or unsupported input. 429 means a rate limit was reached. Error handling and rate limits.