Fieldmotion API Getting started

Assets

List asset custom values

POST /a/Assets_listCustomValues

List distinct custom-field keys and labels found in all asset-type legacy templates.

When to use this endpoint

Use Assets_listCustomValues when building an export or filter field chooser across asset types.

Authentication and permissions

The request must authenticate with signed API-key fields or a logged-in CRM session. The handler requires login or an established tenant database context and performs no additional Asset-page or role-permission check unless the page says otherwise.

Every query and write uses the authenticated tenant’s tables. CRM1 and CRM2 may hide actions through client-side permissions that these collection routes do not repeat.

Parameters

This endpoint has no operation-specific parameters.

Example request

$fields = FM_api('Assets_listCustomValues');

Example response

[
  {"name": "inspection_class", "label": "Inspection class"}
]

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

  • Every asset type is inspected with no archived/deleted filter. Template pages and draggable fields retain database traversal order.
  • When field_name is absent, the display label becomes the field key. The first occurrence of a key wins; later labels for the same key are ignored.
  • Malformed template structures are not fully guarded and can emit warnings. There is no pagination.

See it in Fieldmotion

CRM1

No direct production CRM1 string caller was found; legacy export tooling obtains related custom-field definitions through Asset Type calls.

CRM2

No direct production CRM2 string caller was found; CRM2 uses AssetTypes_getCustomFields for current import/export field selection.

Related endpoints