- Mock serverhttps://otm-api-spec.redocly.app/_mock/api/5.9/otm/api/v5/actions/{UUID}
- https://example.comhttps://example.com/api/v5/actions/{UUID}
curl -i -X GET \
'https://otm-api-spec.redocly.app/_mock/api/5.9/otm/api/v5/actions/{UUID}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'Returned the entity with the provided UUID
Uniquely identifies this entity. A URI can be assigned by the client to indicate where more information can be retrieved. Note that every entity always has a unique EntityId. However since, OTM5.2 it is not required to send it in the request. One can be generated for you by the server.
The last modified date of this entity. If none is given the creation date is used instead.
The context events provides some optional information about the events that can provide additional information on the current state of this entity.
For example: your system might send ETA information for the arrival of a vehicle on a location. To make it clear what caused this ETA to be updated, we can include some information about what caused this ETA update by including an event as context. If your ETA update was caused by a location update, this event can be included as context. If the ETA was caused by a traffic accident on the route of the vehicle, you can include that event in the context.
Standardized identifiers of this entity as known in external systems. Use this to exchange repeatable partner or system specific identifiers without overloading externalAttributes.
[ { "id": "AAA", "scheme": "CAS" } ]
A lifecycle models when the data in the action is taking place. You can provide the same action in multiple lifecycles to model how it changes over time. For example the planned and realized time of an action taking place can differ because of unforseen circumstances (such as traffic jams).
The result of the action, can only be present in the actual or realized lifecycles. The result has a required status and optional additional info, like a remark and reason (in the case of failure).
The sequence number of this action within the entity it is taking place. Can be used to indicate order when no times are present
{ "uuid": "047cfa4d-fd8b-47ba-b8e9-87067294d2fa", "entityType": "consignment", "associationType": "reference" }
Documents that are relevant for this action. Such as a proof-of-delivery photo, or scanned CMR.
The time at which the actions starts in ISO format.
The time at which the action is completed in ISO format.
The recurrence of the date time, should only be set when timeFormat is set to recurringDateTime. The recurrence follows the Recurrence Rule specification
The duration of this action/event, should only be set when timeFormat is set to duration. The duration follows the ISO 8601 specification
{ "id": "e81a7aa3-23a6-4089-b916-52b854c7b6f1", "lifecycle": "planned", "remark": "loading a consignment", "consignment": { "uuid": "047cfa4d-fd8b-47ba-b8e9-87067294d2fa", "entityType": "consignment", "associationType": "reference" }, "startTime": "2021-06-23T14:00:00Z", "endTime": "2021-06-23T14:15:00Z", "constraint": { "entity": { … }, "associationType": "inline" }, "actionType": "load" }