Asset creation options

Request#

GET /api/v1/assets/options

Requires assets:create. See token permissions. Every listed permission is required for this endpoint.

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

Query parameters#

No query parameters are required.

Example#

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

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

Response#

200 OK. Illustrative response excerpt. The available categories, fields, and plan capacity depend on your organization; additional creation choices are described below.

{
  "data": {
    "plan": {
      "limit": 100,
      "remaining": 75
    },
    "categories": [
      {
        "id": 7,
        "name": "Equipment",
        "fields": []
      }
    ]
  }
}

Behavior and constraints#

Returns categories with id, name, and fields (id, name, type, required), plus plan capacity and creation choices. Other keys include conditions, acquisition_types, billing_frequencies, and permissions. Use the dedicated action endpoints for condition, acquisition, or assignments; these fields cannot be sent to inventory POST.

Errors#

401 means the token is missing, expired, revoked, or not a customer API token. 403 means a required permission or administrator access is missing. 429 means a rate limit was reached. See error handling and rate limits.