Reprocess Inbound Event
POST/api/channel-partners/inbound-events/:id/reprocess
Reprocess a single inbound event: marks it in flight and queues a background job that replays the event's stored request payload through the same processing the original request performed. Returns immediately with the event in processing; the outcome (processed with the linked sales order, or failed with the error) is written asynchronously, so re-read the event to see the result.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
The payload is re-validated on replay, so an event that failed because it referenced something that did not exist at the time (a renamed SKU, a missing customer) succeeds once that is corrected — and fails again with the current errors if it is not. Replaying an event whose order already exists on the channel links that order instead of creating a duplicate. Returns 422 if the event has already been processed.
Authentication: Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.