Skip to main content
GET
Get a job
Some requests finish in the background. They answer 202 with a job, and you read the job here until it ends. The requests that start a job are: Use the _id of the job from that response as jobId. Call this endpoint every few seconds until status is COMPLETED or FAILED. Every call counts toward your rate limits.
A job reports only its status. It has no result for each item, and COMPLETED means the job ran to the end. After an ingest, read the devices and points back to confirm what was stored.
A job belongs to the building that started it. Reading it under another building returns 404.

Authorizations

Authorization
string
header
required

Paste an access token from Create an access token. Tokens expire, so request a new one if you receive 401.

Path Parameters

buildingId
string
required

Building identifier from List buildings.

jobId
string
required

Response

The job.

_id
string
organizationId
string
createdAt
string
read-only

Date and time in UTC, with a numeric offset and no colon, for example 2026-10-28T13:51:31+0000.

Example:

"2026-10-28T13:51:31+0000"

updatedAt
string
read-only

Date and time in UTC, with a numeric offset and no colon, for example 2026-10-28T13:51:31+0000.

Example:

"2026-10-28T13:51:31+0000"

name
string
description
string
status
enum<string>
Available options:
PENDING,
PROCESSING,
PROCESSED,
COMPLETED,
FAILED,
CANCELED
errorMessage
string