Long Running Operations
3 items
- Note Designing the Status Endpoint for a Long-Running API The status endpoint is a contract. Publish a small, stable state vocabulary instead of your internal states, report a failed job as a successful status call, and pick one status code convention and hold it.3 min
- Note Assigning Operation IDs When Your API Returns a 202 Using the client's ID as the operation ID will eventually point one customer at another customer's job. Key uniqueness on the client plus their value, and enforce authorization on every status call.5 min
- Note What 202 Accepted Actually Means for a Long-Running API A 202 is as easy to return as a 200. What it commits you to is validating before you accept, publishing a way to track the work, and having an answer ready when the work finishes and nobody is listening.4 min