ActionSessionDate
Questi contenuti non sono ancora disponibili nella tua lingua.
Manage action session dates, which represent the scheduled or actual dates for specific action sessions (such as training, maintenance, or health checks).
You can create, update, delete, and search for action session dates with advanced filtering and pagination.
- Version
- 2.0.0
- OpenAPI version
- 3.0.0
Operations
Sezione intitolata “Operations” POST /v2/action-session-date/index
Returns a paginated and filterable list of action session dates.
Use POST to allow complex filters via JSON payload.
Request Body
Sezione intitolata “Request Body ”Parameters for searching action session dates
object
object
Additional data
The field of the model to sort the list for, use a minus to revert the sort. Es -name is to require the sort in reverse order
The field establishes whether to also include historized elements that are no longer active in the results. If you leave this parameter empty the response returns only actual entries.
Example
{ "filter": { "date_begin": "2024-01-01", "date_end": "2024-12-31" }, "per-page": 10, "page": 1, "sort": "date_begin"}
Responses
Sezione intitolata “ Responses ”List of action session dates
object
Additional data
Example
{ "action_session_date_id": "date-1", "action_session_id": "sess-1", "date_begin": "2024-01-10T09:00:00Z", "date_end": "2024-01-10T17:00:00Z", "subtenant_id": "sub-1", "tenant_id": "ten-1"}
Headers
Sezione intitolata “Headers ”Current page
Total number of pages
Number of items per page
Total number of items
POST /v2/action-session-date/create
Create a new action session date by providing the required details.
Request Body required
Sezione intitolata “Request Body required ”Action session date object to be created
object
Additional data
Example
{ "action_session_id": "sess-1", "date_begin": "2024-03-01T09:00:00Z", "date_end": "2024-03-01T17:00:00Z", "subtenant_id": "sub-1", "tenant_id": "ten-1"}
Responses
Sezione intitolata “ Responses ”Action session date created successfully
object
Additional data
Example
{ "action_session_date_id": "date-3", "action_session_id": "sess-1", "date_begin": "2024-03-01T09:00:00Z", "date_end": "2024-03-01T17:00:00Z", "subtenant_id": "sub-1", "tenant_id": "ten-1"}
GET /v2/action-session-date/view/{id}
Retrieve an action session date by its unique ID.
Path Parameters
Sezione intitolata “Path Parameters ”ID of the action session date to retrieve
Responses
Sezione intitolata “ Responses ”Action session date found
object
Additional data
Example
{ "action_session_date_id": "date-1", "action_session_id": "sess-1", "date_begin": "2024-01-10T09:00:00Z", "date_end": "2024-01-10T17:00:00Z", "subtenant_id": "sub-1", "tenant_id": "ten-1"}
Action session date not found
DELETE /v2/action-session-date/delete/{id}
Delete an action session date by its unique ID.
If force=true, all related entities will also be deleted.
Path Parameters
Sezione intitolata “Path Parameters ”ID of the action session date to delete
Query Parameters
Sezione intitolata “Query Parameters ”Force the deletion of the entity and all related entities
Responses
Sezione intitolata “ Responses ”Action session date deleted successfully
If force=false, the operation is interrupted and the list of connected entities that will be deleted in case of confirmation (force=true) is returned
PUT /v2/action-session-date/update/{id}
Update an existing action session date by its unique ID.
Path Parameters
Sezione intitolata “Path Parameters ”ID of the action session date to update
Request Body required
Sezione intitolata “Request Body required ”Action session date object with updated data
object
Additional data
Example
{ "date_begin": "2024-04-01T09:00:00Z", "date_end": "2024-04-01T17:00:00Z"}
Responses
Sezione intitolata “ Responses ”Action session date updated successfully
object
Additional data
Example
{ "action_session_date_id": "date-1", "action_session_id": "sess-1", "date_begin": "2024-04-01T09:00:00Z", "date_end": "2024-04-01T17:00:00Z", "subtenant_id": "sub-1", "tenant_id": "ten-1"}
Action session date not found