Get Jobs

Filter based On priority of the Job, Allowed:URGENT,HIGH,MEDIUM,LOW

Filter based on customer using customer UIDs

Filter based on category using category UIDs

Used for search

Filter on job tags

Filter based on job status. Only the status uid works (not the status name) — sending a name like "New" returns 200 with 0 rows rather than resolving it or erroring. Get the uid from GET /jobs/status/{category_uid}.

Filter based on job schduled from date

Filter based on job scheduled to date

Filter based on job updated at date

Filter based on job updated at from. Requires a full timestamp in one of: YYYY-MM-DDTHH:mm:ssZ, YYYY-MM-DD HH:mm:ss, YYYY-MM-DDTHH:mm:ss.SSSZ, YYYY-MM-DD HH:mm:ss.SSS. A plain date (e.g. 2026-09-01) is rejected with 400 "Invalid Updated Date" — unlike filter.created_at_from/to, which accept a plain date. Both bounds must be sent together — sending only one silently applies no filter at all (not treated as an open-ended range), with no error.

Filter based on job updated at to. Both bounds must be sent together — sending only one silently applies no filter at all (not treated as an open-ended range), with no error.

Filter based on assigned users on job

Filter based on assigned teams on job

Filter based on created by date

Filter based on custom field. Expects JSON: {"label": "<custom field label>", "value": "<value>"}. An optional third key, "is_regex": true, matches value as a case-insensitive regex instead of exact equality (undocumented elsewhere). A non-JSON string returns 400 "Invalid Format"; valid JSON with different keys (e.g. field_name/field_value) returns 200 with 0 rows rather than an error.

Filter based on asset using asset UIDs

Filter based on ppm uising ppm UIDs

Filter based on service contract using service contract UIDs

Filter based on job UIDS

Filter based on customer feedback, Allowed: 'HAPPY', 'NEUTRAL', 'UNHAPPY', 'VERY_HAPPY', 'VERY_UNHAPPY'

Filter based on recurrence job UIDs

Filter recurrence job

Filter based on job type. Allowed: 'NEW', 'REVISIT'

Filter based on job due date

Filter based on job due date

Filter based on scheduled date

Filter based on property using Property UIDs

Filter based on organisation using organization UIDs

Filter based on job created at date

Filter based on job created at from date. Accepts a plain YYYY-MM-DD date (expanded to 00:00:00/23:59:59 in the company's timezone) — unlike filter.updated_at_from/to, which require a full timestamp. Both bounds must be sent together — sending only one silently applies no filter at all (not treated as an open-ended range), with no error.

Filter based on job created at to date. Both bounds must be sent together — sending only one silently applies no filter at all (not treated as an open-ended range), with no error.

Filter based on status

Filter based on job route

Filter based on parent job using JOB UIDs

Filter Deleted jobs max of 90 days

Filter based on job work order number

Filter based on route enabled for job

Filter based on delayed job

Filter based on invoiced jobs

Filter based on invoice status jobs

Filter based on Job status

Page number

Maximum allowed 1000

Allowed Keys: DESC, ASC

Allowed Keys: work_order_number, job_priority, scheduled_start_time, due_date Note: created_at is NOT one of the allowed keys here, despite being a common first guess — sending it returns 400 "Invalid Sort By Value".

Allowed Keys: scheduled_date, created_date, current_status_updated_at