Fieldmotion API Getting started

Communications

Delete one notice

POST /a/Notice_delete

Permanently delete one notice owned by the current user.

When to use this endpoint

Use Notice_delete for the CRM1 detail dialog’s single-notice delete action. CRM2 uses the generic-audited Notice_deleteData route.

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

ParameterTypeRequiredDescription
idInteger-compatibleYesNotice ID. It must convert to an integer of at least 1.

Example request

$result = FM_api('Notice_delete', [
	'id' => '49018',
]);

Example response

{"ok":1}

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.
{"error":"missing or invalid parameter: id"}id is absent or converts below 1.

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

Behaviour and edge cases

  • Ownership is enforced in the delete statement. An unknown ID or another user’s ID is ignored and still returns success.
  • CRM-originated and app-push notices are treated alike; metadata source is not filtered.

Side effects

  • Hard-deletes the matching row only. User notice checkpoints and counters are not recalculated.

See it in Fieldmotion

CRM1

Open a notice in the CRM1 notice widget and choose delete.

CRM2

No direct CRM2 caller was found; its Notifications page uses Notice_deleteData.

Related endpoints