Fieldmotion API Getting started

Jobs: lookups and details

Count open jobs

POST /a/Jobs_countIncomplete

Count all active jobs with a zero completion code for the CRM header badge.

When to use this endpoint

Count all active jobs with a zero completion code for the CRM header badge.

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

This endpoint has no operation-specific parameters.

Example request

$count = FM_api('Jobs_countIncomplete');

Example response

{"ids":"12"}

Errors and unusual responses

ResponseCondition
{"error":"not logged in"}No authenticated tenant context is available. Invalid signed credentials can be rejected by the dispatcher before the handler runs.

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

Behaviour and edge cases

  • The handler checks DBP for authenticated tenant context. It counts every nondeleted tenant job where NOT is_complete is true: zero only, not every state other than Complete.
  • No assignee, current-user, department, date or on_app filter is applied. Null completion values do not satisfy the zero predicate.
  • ids is a database count, normally a JSON string. A query failure can return {ids:false}; it is not wrapped as an error. There is no paging or write.

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

The CRM2 header calls Jobs_countIncomplete to populate its incomplete-job badge. Refresh the page and filter the initial request.

Related endpoints