Jobs: lookups and details
Retrieve a job’s current postal address
/a/Job_getAddress
Resolve the current customer postal address for one active job, including the asset-owner fallback.
When to use this endpoint
Resolve the current customer postal address for one active job, including the asset-owner fallback.
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_getAddress', ['id' => '1042']);
Example response
{"county":"Antrim","country":"GBR","street_address1":"1 Service Road","street_address2":"","town":"Belfast","postcode":"BT1 1AA"}
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"} | id is absent or nonpositive. |
false | The active job or asset is missing, no customer can be resolved, the customer query has no row, or a query fails. |
Legacy application errors may be returned with HTTP 200. Check the decoded response for error, not only the HTTP status.
Behaviour and edge cases
- Only the job lookup excludes deleted rows. Related customer and asset lookups do not exclude deleted rows.
- For customer_type=1, the asset is found by id OR appId. A nonzero customer-location assignment (location_type=1) wins; otherwise the asset owner supplies the customer. There is no recursive asset-location traversal here.
- The asset id/appId lookup has no explicit ordering when both could match different rows. Other customer types are not validated and follow the direct customer-ID path.
- Returns exactly the six address columns shown. No name, coordinates, city/state, historical snapshot, paging or mutation is added.
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
Job_getCustomerDetailsreturns the job’s cached/historic customer snapshot and can repair it.Job_getLocationresolves current map coordinates using a different asset-location policy.