Events

An event is one entry in the project's audit trail. Every change made through the workspace or the API is recorded, and this resource reads that record. Events are written by the system: there is no endpoint to create, change or delete one.

Endpoints

<event_id> is an event identifier, prefixed evnt_.

The event object

related.table names the kind of record and related.id the record itself, so you can follow an event back to the app, key, file or membership it concerns. There is no updated_at: an event is written once and never revised.

Note — details is a decoded JSON value, never a string. Read it as a container and test for the key you want rather than comparing it against "". Most events record no extra context, and an empty one comes back as [].

List the events

GET /v1/event returns the project's events, newest first, at most 100.

curl https://api.thinkhx.com/v1/event \
  -H "Authorization: Bearer sk-project-YOUR_KEY"

{
  "code": 200,
  "title": "OK",
  "response": {
    "object": "list",
    "data": [
      {
        "id": "evnt_c3f80a25e719bd46a08f",
        "object": "event",
        "type": {
          "id": "evty_48b62f75d0fe49d4db23",
          "name": "File deleted"
        },
        "related": {
          "table": "file",
          "id": "file_d81e4afa6c8bf11fa881"
        },
        "origin": "api",
        "ip_address": "203.0.113.24",
        "details": [],
        "created_at": 1754209800
      }
    ],
    "total": 1
  }
}

Read one event

GET /v1/event/<event_id> returns a single event of your project. An event of another project gives 404 and Event not found.

curl https://api.thinkhx.com/v1/event/evnt_c3f80a25e719bd46a08f \
  -H "Authorization: Bearer sk-project-YOUR_KEY"

Note — The listing is capped at the 100 most recent events and takes no paging parameters, so it is a recent-activity feed rather than a full history. Read the events you care about as they appear if you need to keep them.

origin tells you which surface a change came from, so an entry made by one of your keys is distinguishable from one made by a colleague in the workspace.