Skip to main content
muveya does not send webhooks today. There is no operation to register a URL, no event is pushed to your systems and there is no signing secret to manage. To follow changes, poll the API as described on this page.
If your integration needs push notifications, write to team@muveya.com and describe the events you need. When webhooks become available they will be announced in the changelog.

What to poll

Plan your polling budget

Each key has 120 requests per 60 seconds, shared by every operation (see Rate limits). A budget for one integration could look like this: Keep a margin for retries and for manual checks with the same key, or give each job its own key.

Good practices

  • Filter by status to read only the orders or deliveries you are waiting for, instead of scanning everything.
  • Remember what you saw. Store orderId with its last status and version, and fulfillments with their last updatedAt. Act only when they change.
  • Expect to see a change more than once, or late. Make your processing idempotent: handling the same status twice must be harmless.
  • Read whole lists with limit=200 and follow nextCursor to the end (see Pagination).
  • Do not overlap runs. Start the next poll only when the previous one has finished.
  • Back off on 429. Wait for Retry-After before the next request.

Example: detect order status changes