Fieldmotion API Getting started

Communications

List current-user notices

POST /a/Notices_list

Return a lightweight unpaged list of every notice owned by the current user.

When to use this endpoint

Use Notices_list for the legacy CRM1 notice widget. For a paged/filterable history use Notices_getDataTable.

Authentication and permissions

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

The read or write is limited to the authenticated tenant. Notice endpoints that say “current user” use the authenticated session user ID within that tenant.

Parameters

This endpoint has no operation-specific parameters.

Example request

$notices = FM_api('Notices_list', []);

Example response

[{
  "id": "49018",
  "subject": "Policy update",
  "due_date": "0",
  "status": "0",
  "cdate": "1790848200"
}]

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.
[]The current user has no notices.

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

Behaviour and edge cases

  • There is no pagination, limit, filter, or SQL ordering. CRM1 sorts the returned rows by creation timestamp and then ID in the browser.
  • The response omits body, metadata, owner, platform, and other stored fields. Call Notice_get for the selected row’s body.
  • Both CRM-originated and app-push notices are included because source metadata is not filtered.

See it in Fieldmotion

CRM1

Open the taskbar notice widget. CRM1 calls this endpoint, sorts all rows newest-first locally, and renders each subject.

CRM2

No direct CRM2 caller was found; CRM2 uses Notice_checkNew for the bell and Notices_getDataTable for history.

Related endpoints