This is #15, or a bare-minimum specification of them.
There's really only two things which may error:
POST /exercise should need to return a message with validation errors and these requests are NOT retryable without modification, there may also be transient retryable errors.
GET /status may have transient failures, and will also have non-transient errors for things like "this request ID doesn't exist" or "invalid authentication" type of errors.
I really would like these to map closely to HTTP response codes; not sure if there's an existing standard I can include by reference, but I don't feel like itemizing a bunch of 4XX and 5XX codes until we start implementing, I'm much more interested in just getting the shape specified.
This is #15, or a bare-minimum specification of them.
There's really only two things which may error:
POST /exerciseshould need to return a message with validation errors and these requests are NOT retryable without modification, there may also be transient retryable errors.GET /statusmay have transient failures, and will also have non-transient errors for things like "this request ID doesn't exist" or "invalid authentication" type of errors.I really would like these to map closely to HTTP response codes; not sure if there's an existing standard I can include by reference, but I don't feel like itemizing a bunch of 4XX and 5XX codes until we start implementing, I'm much more interested in just getting the shape specified.