Retry Webhook Event
POST/api/shipstation/integration-instances/:integration_instance/webhook-events/:webhook_event/retry
Queues the webhook event for reprocessing by dispatching a background job. Typically used on events whose processed flag is false and error_message is set (e.g. a transient ShipStation API failure during the resource fetch).
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
The job re-runs the standard processing path: fetch the resource from ShipStation, apply the fetched payload (order/shipment linkage), then mark the event processed or record a new error.
Returns 404 if the event does not belong to the given integration instance.
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.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.