Re-process Webhook Event
POST/api/shiprush/instances/:integration_instance/webhooks/:webhookEvent/re-process
Replay a failed/unprocessed shipnotify: re-resolves its order and re-mints the SalesOrderFulfillment. Only a shipnotify event can be reprocessed — a credential_failed / duplicate / export_rejected row is informational and rejected with 422. Returns the refreshed event.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Path parameter:
- instance: the numeric ID of the ShipRush integration instance.
- webhookEvent: the event id.
No request body is required. Returns 404 when the event does not exist or belongs to a different instance; 422 when the event is not a shipnotify.
Authentication: Requires a 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.