Webhooks

Fiddle doesn’t send outbound webhooks yet. There’s no endpoint for registering a callback URL, and Fiddle won’t POST events to your systems when records change.

To keep an external system in step with Fiddle, poll the REST API on a schedule instead.

Poll for new records

Order, lot, and work order lists return the newest records first by default (sortBy=createdAt, sortDirection=desc). Request the first page on a schedule and stop when you reach a record you’ve already processed:

curl "https://fiddle.io/rest/api/v2/sales-orders?size=50" \
  -H "X-API-Key: YOUR_API_KEY"

The response lists orders under salesOrders. Store the IDs you’ve handled, and fetch the next page only if every order on the current page is new.

The same pattern works for /purchase-orders, /inventory-lots, and /work-orders.

Poll responsibly

• Every five to fifteen minutes is enough for most order and inventory syncs.
• Stay under the rate limit of 100 requests per minute per key, and back off on a 429.
• Make your handler idempotent, so processing the same record twice does no harm.

Connecting a store such as Shopify? Use Fiddle’s built-in integrations instead of polling. They import orders for you.

Next steps

See common API recipes for ready-to-run requests.