Get an organization user

Request#

GET /api/v1/users/{user}

Requires users:read. 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.

user is the numeric ID of a current member of the token’s organization. This is a login user, distinct from an inventory person.

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/42" \
  --header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
  --header "Accept: application/json"

Response#

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

{
  "data": {
    "id": 42,
    "name": "Alex Morgan",
    "email": "[email protected]",
    "is_active": true,
    "is_admin": false,
    "permissions": {
      "can_create_assets": false,
      "can_create_subscriptions": false,
      "can_create_people": false,
      "can_create_locations": false,
      "can_bulk_import": false,
      "can_manage_asset_categories": false,
      "can_manage_subscription_categories": false,
      "can_manage_asset_events": false
    },
    "asset_category_ids": [
      7
    ],
    "subscription_category_ids": []
  }
}

Behavior and constraints#

User responses contain id, name, email, is_active (global, read-only), is_admin (this organization), the eight stored permissions flags, and asset_category_ids / subscription_category_ids restricted to this organization. An empty category list means unrestricted access for that resource type. Administrators have full access regardless of their stored flags. Passwords, authentication tokens, two-factor secrets, personal profile preferences, and other organization memberships are not returned.

Use permission options to look up category names and supported permission fields. That lookup requires users:permissions.

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.