List jobs

GEThttps://api.fieldtask.example/public/v1/jobs

Permission: jobs:read
Pagination: Cursor, up to 100 per page
Also available as: fieldtask_list_jobs

Returns the jobs in your organization, oldest first by default, one page at a time.

You can list every job, the jobs scheduled on one day, or the single job that has a given external_reference. Lists show current data, so a job created or changed while you page through may or may not appear.

Permissions

Permission	Dependency in the permission map
`jobs:read`	No dependencies

Some fields are only included when the connection holds other read permissions too. See Fields that depend on permissions.

Request

Responses

Response Headers

Cache-Control

Responses must not be cached.

X-Request-ID

Server-generated request correlation ID.

Filtering

Use at most one filter:

Parameter	Returns
none	All jobs, including unscheduled ones.
`scheduled_date`	Jobs whose time slot overlaps that calendar day in your organization's time zone. Send `today` or a date such as `2026-11-10`.
`external_reference`	The one job created through your client application with that exact reference, or an empty list. It can't be combined with any other parameter, including `page_size`.

About scheduled_date:

A job is included if any part of its time slot falls on that day, so an overnight job appears on both days.
Unscheduled jobs aren't included. Recurring jobs aren't expanded into separate occurrences.
The response's page.schedule_filter shows the date and time zone the server used, which is useful when you send today.

Pagination

page_size sets the number of jobs per page, from 1 to 100. The default is 25.
ordering is created_at (oldest first, the default) or -created_at (newest first).
When page.has_more is true, request page.next_page_url with the same Authorization header. It keeps your page size, ordering and filter. It's null on the last page.
If you build URLs yourself, pass page.next_cursor as cursor and keep every other parameter unchanged. Cursors expire within 24 hours and only work with the query and connection that produced them.

To change the filter or ordering, start again without a cursor.

Fields that depend on permissions

Each job always includes its own fields, such as id, name, status, schedule and customer_id. These fields need more:

Field	Included when the connection also has
`customer`	`customers:read`
`location`	`customers:read` and `customer_locations:read`
`assignee_member_ids`, `assignees`	`members:read`
`revision`	No extra permission, but only where FieldTask has enabled change tracking for jobs

FieldTask can also withhold a field everywhere until it's published for your environment, so treat any field not listed as required in the response schema as optional.

The customer, location and assignees summaries show those records' current names and contact details. Changes to them don't change the job's revision.

job_value is the current sum of quantity × unit price over the job's line items, as a decimal string in currency. It includes items that are kept on the job but marked inactive, as the job total in FieldTask does, so it can differ from the sum of the items that List job items returns. The number of decimal places isn't fixed (for example "0.00" or "185.0000"), so parse it as a decimal rather than comparing strings. It isn't an amount paid.

Job status

status is one of unscheduled, scheduled, in_progress, completed, missed or cancelled. unknown means the job has a status this API version doesn't recognize; handle it rather than failing.

Errors

Status	`code`	Meaning	What to do
400	`invalid_query`	The query string has an unknown, repeated or invalid parameter.	Send only the documented query parameters, each once.
400	`invalid_cursor`	The cursor is malformed, was changed, or belongs to a different query, connection or page size.	Use `next_page_url` or the cursor exactly as returned, with the same query. To change the query, start again without a cursor.
401	`invalid_token`	The bearer token is missing, malformed, expired, revoked or issued for a different resource (for example an MCP sign-in).	Send a current REST API token or REST OAuth access token as `Authorization: Bearer …`.
403	`api_access_not_enabled`	FieldTask hasn't enabled API access for this organization, or has disabled it.	An owner or admin requests access in Settings → API connections.
403	`insufficient_scope`	The connection lacks a permission this request needs. `error.code` is `missing_permission`.	Add the permission named in `error.message` to the connection.
404	`resource_not_found`	The record doesn't exist or isn't visible to this connection, the feature isn't available in this environment, or the URL is wrong.	Check the ID, the API origin and the path (no trailing slash).
405	`method_not_allowed`	This path doesn't accept the HTTP method, or the create isn't enabled in this environment. The `Allow` header lists the methods that are.	Use a method listed in `Allow`.
429	`rate_limit_exceeded`	Too many requests in the current minute, or too many concurrent requests, for the organization or connection.	Wait for `Retry-After` seconds, then retry.
429	`daily_quota_exceeded`	The organization or connection has used its daily allowance for this kind of request. Allowances reset at 00:00 UTC.	Wait for `Retry-After` seconds, or check remaining allowance in Settings → API connections.
503	`temporarily_unavailable`	The service couldn't complete the request.	Retry with exponential backoff. Retry creates with the same key and body.

Request

# Jobs scheduled today, in your organization's time zone.
curl --get "$FIELDTASK_API_ORIGIN/public/v1/jobs" \
  --header "Authorization: Bearer $FIELDTASK_API_TOKEN" \
  --data-urlencode "scheduled_date=today" \
  --data-urlencode "page_size=100"

Response200 OK

First page with more results

{
  "data": [
    {
      "id": "66666666-6666-4666-8666-666666666666",
      "name": "Inspect rooftop unit",
      "description": "Annual inspection. Ask at reception for roof access.",
      "job_type": "field_job",
      "job_number": null,
      "status": "unscheduled",
      "schedule": {
        "mode": "unscheduled"
      },
      "customer_id": "11111111-1111-4111-8111-111111111111",
      "customer": {
        "id": "11111111-1111-4111-8111-111111111111",
        "name": "Example Property Services",
        "email": "facilities@example.com"
      },
      "location_id": null,
      "job_value": "0.00",
      "currency": "USD",
      "revision": 1,
      "created_at": "2026-11-03T14:05:12.481Z",
      "updated_at": "2026-11-03T14:05:12.481Z"
    }
  ],
  "page": {
    "has_more": true,
    "next_cursor": "EXAMPLE_OPAQUE_CURSOR",
    "next_page_url": "https://api.fieldtask.example/public/v1/jobs?page_size=1&cursor=EXAMPLE_OPAQUE_CURSOR"
  }
}

Example values. IDs and times will differ in your organization.

Try itRequest builder

1. Set the base URL to your API origin with Edit. 2. Paste your token. 3. Fill in parameters or the body. 4. Press Send API Request, or copy the request below and run it yourself. Your token is only kept on this page. Sends are real requests: a create makes a real record.

Loading the request builder…

List jobs

Permissions​

Request​

Responses​

Filtering​

Pagination​

Fields that depend on permissions​

Job status​

Errors​

Permissions

Request

Responses

Filtering

Pagination

Fields that depend on permissions

Job status

Errors