-1

The HTTP 202 Accepted response is used to accept a task for background processing, and optionally providing a separate URL for monitoring the progress of the task. All answers and posts I've read about it basically suggest everyone to invent their own response types for the submission and monitoring endpoints.

Does there exist any specifications / proposals / conventions (followed by multiple companies) as to how the monitoring URL is returned (an HTTP header or response payload) or what the structure of the monitoring API response is?

Failing that, does any big names (Google, Twitter, etc) implement this pattern in their public APIs, from which to gain insight?

Sampo
  • 4,308
  • 6
  • 35
  • 51
  • Care to elaborate why this is off-topic / opinionated? I specifically read the instructions on "best practice" questions and phrased exact questions. The first one can be answered by a link to a spec or "No" (as already done). The second can be answered by a link to API docs or "None of the biggest five Internet companies use such APIs". – Sampo Oct 27 '18 at 14:58

1 Answers1

1

Does there exist any specifications for HTTP 202 status monitors?

As far as I can tell, as of October 2018 the answer is no.

If there were a standard, I would expect it to appear as a media type (analogous to RFC 7807: Problem Details ) or as some interesting entries in the Link Relations registry.

Community
  • 1
  • 1
VoiceOfUnreason
  • 52,766
  • 5
  • 49
  • 91