Retry Webhook Event
POST/api/starshipit/integration-instances/:integration_instance/webhook-events/:webhook_event/retry
Queues a background job to reprocess a webhook event — typically one that failed and recorded an error_message. No request body.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Reprocessing re-applies the stored payload as if the webhook had just arrived: the event is matched to a cached order by order number or tracking number, the tracking status is applied (which can update order status, record fulfillment shipment, and push tracking to the sales channel), and the event is marked processed on success or gets a fresh error_message on failure. The job retries up to 5 times with increasing backoff.
Retrying is safe: events already marked as processed are skipped by the background job, so re-queuing a successful event is a no-op.
Returns 404 when the event does not exist or belongs to a different 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
Response Headers
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.