Returns a recent org-wide activity feed (serial events, audit events, stock movements), newest-first.
const url = 'https://app.dev.buildtrace.eu/api/activity?limit=50';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://app.dev.buildtrace.eu/api/activity?limit=50' \ --header 'Authorization: Bearer <token>'Required scope: dashboard:read.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Responses
Section titled “Responses”OK
One entry of the org activity feed, with what a client needs to write it as a sentence: who did it (actorName, actorKind), what happened (type + action), what it happened to (subject, with a human label) and the key facts (details, changes). The same act is never reported twice: where an audit event and a serial event or stock movement record one act, only the richer one is returned.
object
Where the event comes from.
What happened. For audit_event the audit action (e.g. bom.add_line, revision.release, inspection.record); for serial_event the serial event type (RECEIVED, MOVED, QUARANTINED, RELEASED, SCRAPPED, SHIPPED, FIRMWARE_FLASHED); for stock_movement the movement type (RECEIVE, TRANSFER, ADJUST).
Machine-ish one-line summary kept for older clients. Use action, subject and details.
Who did it - the member’s name, the service account’s name, or “System”.
The raw entity type the event was recorded against (e.g. bom_line, serial).
The raw entity id the event was recorded against.
The thing the event is about, which a client links to. Not always the raw recorded entity: a BOM line event is about the parent revision, an inspection about the unit (or the revision for a lot inspection), an upload about the entity the file is attached to.
object
The identifier people use: part code, serial number, build/rework order number, ECO number, device id, location or supplier code, firmware “
The revision label, when type is revision.
The part, when type is part or revision.
The entity no longer exists (or can’t be found in this organization).
Key facts for the sentence. Only the fields that apply to the action are set.
object
Another part involved - the child part of a BOM line, the assembly of a build order.
Revision label of that part, when known (build order assembly).
Quantity (BOM line quantity, build order target, stock moved), plain decimal.
The quantity before an edit.
Unit of measure of the quantity.
For a stock adjustment, true when stock went up.
Inspection result (PASS, FAIL, CONDITIONAL).
Inspection type (INCOMING, IN_PROCESS, FINAL, FIELD).
Location code moved from.
Location code moved to.
Free-text reason given (quarantine, scrap, adjustment, cancellation).
Rework reason code (ECO_RETROFIT, RMA_REPAIR, FIELD_SERVICE, UPGRADE, SALVAGE).
Firmware reported by a unit, “
Serial number of the unit involved (rework order, device).
ECO title.
Numbering scope (SERIAL, LOT, DEVICE, BUILD_ORDER, REWORK_ORDER).
Name of the fleet a firmware version was assigned to.
Identifier of the device a firmware version was assigned to.
Field changes recorded with the event (from/to as display strings).
object
Example
[ { "type": "serial_event", "actorKind": "account", "subject": { "type": "part" } }]Unauthorized
Forbidden