addEvent

Deprecated

This endpoint will stop working on 1 August 2027. Migrate to POST /v1/jobs/{id}/events in the new API; the migration guide has the recommended order of work and the important model differences.

POST /v1/jobs/{id}/events creates a typed JobEvent. The eventType code replaces legacy sigEventCode — look up valid codes from GET /v1/jobs/job-events.

sequenceDiagram
    autonumber
    participant Client
    participant API as Oneserve API
    Client->>API: GET /v1/jobs/job-events<br/>(once — cache the catalogue)
    API-->>Client: [{eventType, label}, ...]
    Client->>API: POST /v1/jobs/{jobId}/events<br/>{date, notes, eventType}
    API-->>Client: 201 Created

Not to be confused with the new /v1/events/* family, which is the OneCore integration/webhook subscription layer (a different concept).

Open POST /v1/jobs/{id}/events in the new API →

View legacy reference

/rest/workflow/job/addEvent/{jobRef}

POST 

Adds a Job Event.

acceptable request representations:

• application/json

event={
  "sigEventCode":"AB",
  "appointmentId":"343",
  "noteId":"33",
  "note":"a note",
  "date":"12-12-2012 12:34:00"
}

See the Workflow API matrix for the full list of endpoints in this category.