/api/v1/assets/{record}/timeline
Assets timeline
Read the finalized history and notes associated with an asset.
Last updated
Request
GET /api/v1/assets/{record}/timeline
Requires assets:read. See token permissions. Every listed permission is required for this endpoint.
Send Authorization: Bearer YOUR_API_TOKEN and Accept: application/json.
record is the numeric asset ID in your token’s organization.
Query parameters
| Field | Type | Usage |
|---|---|---|
page |
integer | Optional. Starts at 1; default 1. |
per_page |
integer | Optional. 1–100; default 25. |
from |
string | Optional. Inclusive UTC date, YYYY-MM-DD. |
to |
string | Optional. Inclusive UTC date, YYYY-MM-DD; cannot precede from. |
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/123/timeline?from=2026-09-01&to=2026-09-07&per_page=25" \
--header "Authorization: Bearer $ASSETCENTER_API_TOKEN" \
--header "Accept: application/json"
Response
200 OK. Example of an empty timeline page showing common pagination fields. The API includes additional pagination links and metadata.
{
"data": [],
"links": {
"next": null,
"prev": null
},
"meta": {
"current_page": 1,
"last_page": 1,
"per_page": 25,
"total": 0
}
}
Behavior and constraints
The example shows a date range with no matching events. Nonempty data entries contain id (type:event_id), event_id, type (asset_event, subscription_event, or person_location_event), event_date, event_type (id, name, slug, category, or null), description, cost (decimal string or null), date_due, created_by, related, created_at, and updated_at.
Events sort by event date descending, event ID descending, and type ascending. Undated events sort last and are excluded by a date filter. tenant_id and account_id are prohibited.
Related asset events require assets:read, and related subscription events require subscriptions:read. Related references contain resource, id, and name only for resources the token can read. Deleted records may retain a historical name with a null ID. Descriptions may contain HTML; sanitize them before rendering as HTML.
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. 429 means a rate limit was reached. See error handling and rate limits.