Timeline for What to include in a (Batch) POST/PATCH results/errors for results for pragmatic REST API
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 7, 2018 at 22:39 | comment | added | Laiv | And you still can send back to client a response body. The one that best suites your needs. | |
| Nov 7, 2018 at 22:32 | vote | accept | peterc | ||
| Nov 7, 2018 at 22:32 | comment | added | peterc | @laiv yes that is a good point that I recently stumbled upon myself. My posts do exactly that, validated and then queued to be async sent to the database server, so a 202 would have been better here. | |
| Nov 7, 2018 at 7:39 | comment | added | Laiv | It might interest 202 Accepted. The representation sent with this response ought to describe the request's current status and point to (or embed) a status monitor that can provide the user with an estimate of when the request will be fulfilled Whether The representation sent with this response ought to describe the request's current status and point to (or embed) a status monitor that can provide the user with an estimate of when the request will be fulfilled means an id, a URL or a whole resource representation is up to you. | |
| Nov 7, 2018 at 3:08 | answer | added | VoiceOfUnreason | timeline score: 4 | |
| Nov 7, 2018 at 2:16 | history | asked | peterc | CC BY-SA 4.0 |