Retrieve a job’s completion status

When to use this endpoint

Read the saved completion-state code for one active job.

Authentication and permissions

Authenticate with signed API-key fields or a logged-in CRM session. These calls use the authenticated account’s data; the handler has no additional job-page, department, assignee or client-admin permission check unless stated below.

Parameters

Parameter	Type	Required	Description
`id`	Integer string	Yes	Job ID, converted with intval; the result must be positive. This selects a physical job ID, not an app ID or job reference.

Example request

$result = FM_api('Job_getStatus', ['id' => '1042']);

Example response

{"is_complete":"0"}

Errors and unusual responses

Response	Condition
`{"error":"not logged in"}`	No authenticated tenant context is available. Invalid signed credentials can be rejected by the dispatcher before the handler runs.
`{"error":"missing or invalid parameter: id"}`	Invalid ID; checked before login.
`{"error":"job does not exist"}`	The active job query returns false, including not-found and query failure.

Legacy application errors may be returned with HTTP 200. Check the decoded response for error, not only the HTTP status.

Behaviour and edge cases

Returns an object with the raw database is_complete value, normally a JSON string. It does not return user_status, workflow state or a translated status label.
The field represents the stored completion code, not a boolean. It is not constrained by this read. No schedule/assignee/department filter, pagination or write is applied.

See it in Fieldmotion

CRM1

No direct CRM1 caller was found in the reviewed source. Use this focused API request when the full job editor payload is unnecessary.

CRM2

No direct CRM2 caller was found in the reviewed source. For batched job fields, see Jobs_getById.

Related endpoints

Jobs_countIncomplete counts active jobs whose is_complete is zero.
Jobs_getById can select is_complete and date_completed_e together.