Fieldmotion API Getting started

Asset maintenance

List maintenance descriptions

POST /a/AssetMaintenance_listNames

List the distinct maintenance descriptions already stored in the tenant.

When to use this endpoint

Use AssetMaintenance_listNames to populate CRM1’s description picker when creating a maintenance schedule or renaming an existing one.

Authentication and permissions

The request must authenticate with signed API-key fields or a logged-in CRM session. The handler performs no additional page or role-permission check.

The lookup and any write use the authenticated tenant; an ID from another tenant cannot be addressed through this call.

Parameters

This endpoint has no operation-specific parameters.

Example request

$names = FM_api('AssetMaintenance_listNames');

Example response

[
  {"name": "Filter service"},
  {"name": "Safety inspection"}
]

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

  • Names are deduplicated by the database and ordered ascending using the tenant database collation.
  • Blank and null values are not filtered. Active/inactive schedules and missing/deleted assets are all included.
  • There is no pagination or row limit.

See it in Fieldmotion

CRM1

Open Assets → Maintenance, click Create, or click an existing description. CRM1 calls AssetMaintenance_listNames to build the picker and offers an add-new choice locally.

CRM2

No production CRM2 caller was found; the modern recurrence editor uses free-text recurrence fields.

Related endpoints