Actions Service

Back

Overview

Actions represent tasks or activities assigned to entities (customers or suppliers). They support scheduling, tracking, and completion management.

Actions are used for:

All action operations are tenant-aware and scoped to the current tenant.


Endpoints

Back to Actions

GET

/api/v1/Actions/{id}

Returns a single action by its numeric identifier.

Route parameters:

Behavior:

Authorization:


GET

/api/v1/Actions/entity/{entityId}

Returns a paginated, filterable list of actions for a specific entity.

Route parameters:

Query parameters (pagination):

Query parameters (filters):

Behavior:

Authorization:


GET

/api/v1/Actions/due

Deprecated. Use GET /api/v1/Actions/entity/{entityId} with showComplete=false instead.

Returns all due actions (past due date and not completed).

Behavior:

Authorization:


POST

/api/v1/Actions

Creates a new action.

Request body (CreateActionRequest):

Behavior:

Errors:

Response:

Authorization:


PUT

/api/v1/Actions/{id}

Partially updates an existing action. Fields not included in the request body retain their existing values.

Route parameters:

Request body (UpdateActionRequest):

Behavior:

Errors:

Response:

Authorization:


PATCH

/api/v1/Actions/{id}

Marks an action as completed (sets CompletedAt to the current UTC timestamp).

Route parameters:

Behavior:

Errors:

Response:

Authorization:


DELETE

/api/v1/Actions/{id}

Deletes an action by its identifier.

Behavior:

Errors:

Response:

Authorization:


Notes