Add an asset event

Request#

POST /api/v1/assets/{record}/events

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

Send Authorization: Bearer YOUR_API_TOKEN and Accept: application/json. Send request bodies as JSON with Content-Type: application/json, or as multipart/form-data when uploading attachments. This workflow write requires Idempotency-Key. Reuse the same key only when retrying the same action.

record is the numeric asset ID in your token’s organization.

Query parameters#

This endpoint does not use query parameters.

Request body#

Fetch available values before choosing IDs. IDs and required fields vary by organization.

Example#

Set ASSETCENTER_API_TOKEN as described in the quick start. Replace example record and option IDs with values from your organization. Set IDEMPOTENCY_KEY to a new UUID for this action; keep it for retries.

curl --request POST "https://my.assetcenter.app/api/v1/assets/123/events" \
  --header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
  --header "Accept: application/json" \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: $IDEMPOTENCY_KEY" \
  --data '{"event_type_id":12,"description":"Inspection completed."}'

To upload files, send multipart/form-data instead of JSON. Let curl set the Content-Type header, and send booleans as 1 or 0.

curl --globoff --request POST "https://my.assetcenter.app/api/v1/assets/123/events" \
  --header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
  --header "Accept: application/json" \
  --header "Idempotency-Key: $IDEMPOTENCY_KEY" \
  --form "event_type_id=12" \
  --form "description=Inspected after repair." \
  --form "comments[]=Photos taken on site." \
  --form "attachments[]=@inspection.jpg" \
  --form "attachments[]=@report.pdf"

Response#

201 Created. Illustrative response structure. Event arrays, to-do/space values, and current state depend on the action and the record.

{
  "data": {
    "asset_id": 123,
    "asset_event_ids": [
      901
    ],
    "subscription_event_ids": [],
    "todo": null,
    "tracker_disconnect_pending": false,
    "state": {
      "status": "available",
      "person_id": null,
      "location_id": null,
      "sublocation_id": null,
      "is_in_storage": false,
      "person_loan_due": null,
      "location_loan_due": null,
      "condition_id": null,
      "decommission_event_type_id": null
    },
    "attachments_count": 0,
    "comments_count": 0
  }
}

Behavior and constraints#

Choose an event type from the lifecycle category. System assignments, acquisitions, and decommission events use their dedicated endpoints. Required fields vary with the selected type; supply all fields marked required by options.

Attachments and comments are saved on the event, and attachments_count and comments_count in the response confirm how many were added. Files are stored privately and count toward your plan’s storage; a request that would exceed it returns 422 with a plan error and changes nothing. If any file fails to save, the whole action is rolled back. In a multipart body, send object fields with bracketed keys (such as field_values[12]=Blue) and leave out a field rather than sending null. An Idempotency-Key retry must resend the same files; a different file is a different request and returns 409.

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. 404 means the record or child record is unavailable in this organization. 422 identifies invalid or unsupported input; inspect the errors object when present. 409 indicates a conflicting state or concurrent change; inspect the message and refresh the record before deciding how to proceed. Reusing an idempotency key with a different method, path, or body also returns 409. 429 means a rate limit was reached. See error handling and rate limits.