AssetsLogs

Logs

Retrieve an Asset's Logs #

Method
GET
Endpoint

Retrieves the activity history for an Asset.

Parameters
Name Type Required? Description Details
asset_id Number Yes
The ID of the Asset whose history you want to read.
Use the Asset's record ID.
filter_by_actor_user_id String No
Only return entries written by this user.
Use the opaque actor_user_id from a log entry. Up to 128 characters; treat it as text. Historical IDs can match former users.
filter_by_log_entry_contains_text String No
Only return entries containing this text.
Up to 3,000 characters after trimming surrounding spaces. Text is matched literally; HTML is not converted and search characters are not wildcards.
filter_by_create_timestamp_greater_than_or_equal_to String No
Only return entries at or after this timestamp.
Use an ISO 8601 timestamp. A fractional lower bound starts at the next whole second. Include an offset or Z to state the time zone.
filter_by_create_timestamp_smaller_than_or_equal_to String No
Only return entries at or before this timestamp.
Includes every entry in the displayed second. It must not precede the lower bound.
filter_by_event_id Number No
Only return entries filed under this Event ID in your workspace’s history.
filter_by_event_tab_id Number No
Only return entries filed under this Event tab ID. GET /v1/references/event_tabs lists your workspace's tabs; the Presentations tab is accepted only where your workspace has it.
Allowed values: 1 (Info) | 2 (Booth) | 3 (Staff) | 4 (Travel) | 5 (Assets) | 6 (Shipments) | 7 (Sponsorships) | 8 (Tasks) | 9 (Playbook) | 10 (Attachments) | 11 (Misc. Expenses & Credits) | 12 (Budget) | 13 (ROI) | 14 (Event Settings) | 16 (Binder) | 17 (Copy Event) | 19 (Logs) | 20 (Delete Event) | 21 (Giveaways) | 22 (Special Tab, shown under your workspace's name for it)
filter_by_context_type String No
Only return entries associated with the selected context. Omit to include all contexts. Workspace means an entry with none of the other associations; an entry can belong to more than one other context. Unsupported values are refused. Values are case-insensitive.
Allowed values: workspace | event | task | asset | storage_location
$result_sort String No
Sort entries newest first (the default) or oldest first. The full saved timestamp is used, with the entry ID breaking ties in the same direction. Responses display whole seconds. Unsupported values are refused. Use the values exactly as shown (lowercase).
Allowed values: create_timestamp_desc (newest first) | create_timestamp_asc (oldest first)
$limit Number No
The maximum number of matching entries to return.
One positive whole number. Omit for all matches after $offset; there is no fixed page-size cap.
$offset Number No
The number of matching entries to skip.
Default: 0. Send a nonnegative whole number.
$result_format String No
By default, the response is an object containing list_data and the paging totals (records_found, total_records, has_more). Send array to get just a JSON array of the records, or wrapped_in_array to get the default object inside a one-item array.
Allowed values: array | wrapped_in_array
If-None-Match String No
Send the ETag from an earlier response when checking whether this result changed.
Optional request header. A matching current result returns HTTP 304 with no body; reuse your earlier response. This header compares GET responses. It cannot prevent a conflicting update.

Good to know

Retrieves the visible business history filed under one Asset. Filters work together to narrow its history. Results are ordered newest first by default. This is the selected record’s history, not a combined history of every child record.

Choosing the record

Use the Asset ID to choose the history you want to retrieve. Active and Archived Assets are supported.

Only entries filed under the selected record are included. Sharing or borrowing an Asset does not grant access to its owner’s history.

Only history visible to workspace users is returned. Hidden or technical entries, impersonation activity, IP addresses, device details and security information are excluded.

Filtering by time and context

Returned timestamps use UTC and display whole seconds. Timestamp filters use that displayed precision: the upper bound includes the entire displayed second, and a fractional lower bound starts at the next whole second.

An input with an offset or Z is converted for comparison. A timestamp without an offset is interpreted as US Eastern time. Include an offset when you want an unambiguous instant.

workspace context selects entries with no Event, Task, Asset or Storage Location association. The other contexts select entries with that association, and an entry can have several associations. Every result must still be filed under this selected Asset, so a context filter can legitimately produce no matches.

Paging the result

records_found is the number of rows in this response; total_records is the filtered count before paging. has_more indicates whether more matching rows remain. Results can change while the data is edited.

Omit $limit for all matches after $offset, or use the two options to read smaller pages. There is no fixed page-size cap. This list does not return edit revisions or support changed-since filtering.

Handling errors

This method has no empty-result-on-error option. Invalid inputs retain their error status. If concurrent changes prevent the read, HTTP 409 with error_code=record_changed means you should read again.

Each row has the same fields as an entry from GET /v1/workspace_settings/logs. It does not change the selected record, issue an edit revision or provide a feed of changes and deletions.

Sending filter values

Use the query string, form data or JSON for a text filter that contains a comma.

Checking whether a response changed

Normal API-key and access checks still apply. This header compares the response; it does not authorize access or protect an update.

  1. Save the response body and its ETag header from an earlier GET.
  2. Repeat the same GET, including the same filters and response options, with that ETag in the If-None-Match header.
  3. If the response is HTTP 304, keep using your saved body. If it is HTTP 200, use the new body and ETag.

Reading the actor

actor_user_id is the ID of the user who made the change. actor_display_name is the name saved with the entry at that time; it does not change if the user is renamed later.

Entries recorded by the API have a null actor_user_id and show the label saved with them, such as API.

Code Samples
curl -X GET "https://api.exhibitday.com/v1/assets/logs?asset_id=12345" -H "Authorization: Bearer YOUR_API_KEY"

Example response

{
  "records_found": 1,
  "total_records": 1,
  "has_more": false,
  "list_type": "workspace_log",
  "list_data": [
    {
      "id": 67890,
      "log_entry_created_timestamp": "2026-01-02T08:04:05Z",
      "actor_user_id": "11111111-2222-4333-8444-555555555555",
      "actor_display_name": "Illustrative user",
      "log_entry": "Illustrative user updated the selected record.",
      "event_id": null,
      "event_name": null,
      "event_tab_id": 0,
      "task_id": null,
      "task_name": null,
      "asset_id": 12345,
      "asset_name": "Display stand",
      "storage_location_id": null,
      "storage_location_name": ""
    }
  ]
}
Note: IDs are illustrative; use IDs from your workspace.