Delivery & reliability
HTTP 202 Accepted
HTTP 202 Accepted indicates that a request has been accepted for processing, while processing may still be incomplete when the response is sent.
Also found under: 202 response, Asynchronous acceptance
How it works
Acceptance is a useful boundary for asynchronous APIs: the caller knows the request entered the service's workflow. It is not proof that each downstream action finished. Applications should interpret the response body and implement any business-level completion tracking they require.
In a Pubb integration
Pubb's publish endpoint returns HTTP 202 with success, accepted, channels, publicationId and duplicate fields. That response does not confirm delivery to every connected client or that a person read the event.
Publish an eventA practical example
A backend logs the accepted publication ID after a successful request. A chat application's read marker remains a separate application event generated when a recipient actually reads the message.