Skip to main content
Webhooks let Owlery send updates to your systems the moment something changes, so you don’t have to poll for them. Your team provides an endpoint, and Owlery registers it for you.
Webhooks are included on select plans.

​
Events You Can Receive

See the Shipper Webhooks API reference for the full payload of each event.

​
Set Up Webhooks

Send your Owlery contact:
  • An HTTPS endpoint URL: one URL for every event, or a separate URL per event.
  • The events you want: any of the events above.
  • An authentication header: such as an API key or bearer token (for example, Authorization: Bearer …). Owlery includes it on every request. OAuth 1.0 (as NetSuite uses) also works.
Owlery registers your endpoint, and updates start arriving with the next matching event.

​
Build Your Endpoint for These Rules

  • Each update is one JSON POST, covering a single record or a small batch.
  • Return a 2xx response quickly. Do any heavy processing after you respond.
  • Owlery doesn’t retry. If a request fails, it isn’t sent again. Make sure your endpoint is reliable, and that receiving the same update twice does no harm.
  • Requests aren’t signed. Owlery doesn’t send a signature header. Verify requests with the header or OAuth credentials you gave us.

​
Testing

Webhooks only send from Owlery’s production environment, so the first test uses real activity in your account.