Post leg event
POST/legs/:id/events
This endpoint must be used to alter the state of a leg.
FINISH will end this leg (see (4.6) in process flow) [TO and MP]
Request
Responses
- 200
- 204
- 400
- 401
- 403
- 404
- 503
operation successful
Request was successful, no content to return.
Bad request. See https://github.com/TOMP-WG/TOMP-API/wiki/Error-handling-in-TOMP for further explanation of error code.
Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
The client does not have access rights to the content, i.e. they are unauthorized, so server is rejecting to give proper response. Unlike 401, the client's identity is known to the server.
The requested resources does not exist or the requester is not authorized to see it or know it exists.
In case of temporary malfunctioning, this response can be send (e.g. bluetooth lock jammed). See also https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After
Response Headers
seconds after response
120