Skip to main content
Register a URL and Replo sends it a signed POST each time something happens in your project, so your warehouse, ERP or automation hears about orders and packages without polling. Webhooks are in beta and need API version 2026-11-17.

Before you begin

  • A public https URL that answers within 10 seconds. Replo refuses URLs that resolve to a private network.
  • To manage endpoints through the API, a project API key with webhooks.read and webhooks.write. You can also manage them in Settings → Developers → Webhooks.

Add an endpoint

The response carries secret (whsec_…) once. Store it: Replo keeps it encrypted and never shows it again. An empty events list sends every event type. Each endpoint is pinned to the API version current when you created it (apiVersion). Payloads keep that shape for the endpoint’s whole life, so a later API version never changes what your code receives. To move to a newer version, add a new endpoint and delete the old one.

Event types

data is the same object the matching GET returns in the endpoint’s API version: GET /v1/orders/{orderId} for order events, and one item of GET /v1/orders/{orderId}/fulfillments for fulfillment events. It’s read when the request is sent, so it reflects the resource at that moment, not only the change that triggered it.

The request

Check the signature

Verify every request before you trust it. Sign the raw body exactly as received, before any JSON parsing, compare in constant time, and reject timestamps more than five minutes old so a captured request can’t be replayed.

Answer, retries and ordering

  • Answer with a 2xx within 10 seconds. Do slow work after you answer. A timeout, a connection error, any other status, or a redirect counts as a failed attempt. Replo doesn’t follow redirects and doesn’t read your response body.
  • Retries. A failed delivery is tried 8 times in all, about 24 hours: again after 1 minute, 5 minutes, 30 minutes, 2 hours, 5 hours, 8 hours and 8 hours. After the eighth failure it stops and the delivery shows as failed. Send it again from the delivery log or with POST /v1/webhook-deliveries/{webhookDeliveryId}/redeliver, which restarts the schedule.
  • Duplicates. A request can arrive more than once. Use Replo-Webhook-Id as a dedupe key.
  • Ordering isn’t guaranteed. Two events about the same package can arrive out of order. For fulfillments, ignore an event whose data.updatedAt is older than what you already have. For orders, compare the body’s created, or fetch the order again.
  • Turned off after 7 days of failures. An endpoint with no successful delivery for 7 days is turned off (enabled: false, disabledReason: "failing") and the person who created it gets an email. Fix your endpoint, then turn it back on in Settings or with PATCH /v1/webhook-endpoints/{webhookEndpointId} and {"enabled": true}. Deliveries still waiting for a retry are sent within the hour; failed ones can be sent again from the delivery log.

Manage endpoints

Rotating takes effect on the next request, so deploy code that accepts the new secret first. A project can have up to 16 endpoints. In Settings → Developers → Webhooks you can also send a test event: a sample fulfillment.updated, signed like a real one, with your server’s answer shown right away.

Ship from your own tool

Mark orders shipped and keep tracking in sync through the API.

Versioning

How API versions and pinned payloads work.