For administrators · about 20 min

Get notified in your own systems when a package is created or downloaded

Register a webhook so your ticketing, chat or pipeline tooling hears about package events: choose the endpoint, subscribe to topics such as package.created and package.status_changed, verify the signing secret, send a test event, and retry failed deliveries.

You end up with
An HTTPS endpoint of yours that receives signed JSON for the package events you chose, with a delivery log and retry in the admin console.
Plan
Webhooks are available from the Professional plan, per the pricing page.
Updated

Before you start

  • An administrator account.
  • An HTTPS endpoint you control that can accept POST requests. Your organization's webhook target policy may restrict which hosts are allowed; check it under Admin before you start.
  • A place to store the signing secret, such as your secret manager.

Steps

  1. Open Webhooks

    Admin · Webhooks

    Open Admin, then Webhooks, and choose the action to add a new webhook.

  2. Name it and set the endpoint

    Enter a Display Name such as 'Ticketing receiver' and the Endpoint URL of your service. Leave the signing secret blank to have one generated, or paste your own.

  3. Subscribe to events

    Under Subscribed Events pick the topics you need. For package lifecycle use package.created and package.status_changed. For external downloads through public links use package.external_viewed and package.external_file_downloaded. For delivery state use delivery.status_changed. Leave the rest unselected; you can add topics later.

  4. Save the signing secret

    After saving, the console shows the secret once under 'Save the signing secret'. Store it now. Your endpoint uses it to verify each request's signature before trusting the payload.

  5. Send a test event

    Use the webhook's test action. Your endpoint receives a webhook.test event. Confirm it validates the signature and returns a 2xx status.

  6. Trigger a real event

    Admin · Webhooks · Events

    Send a small package. Within moments the webhook's event log shows a package.created delivery and its response status.

  7. Retry when something fails

    A delivery your endpoint rejected or timed out on is listed with its status. Open the event and use Retry once the endpoint is fixed.

How you know it worked

  • The test event arrives with a valid signature and your endpoint returns 2xx.
  • A real package.created event arrives for a package you sent, with the package ID matching the one in Sent.
  • A deliberately failing endpoint shows the failed delivery in the event log, and Retry succeeds after the fix.

If something is off

What you seeWhat to do
Saving fails with a target policy messageThe endpoint host is not on your organization's allowed list. An administrator updates the webhook target policy, then save again.
Events arrive but the signature does not verifyThe secret in your service differs from the one shown at creation. Rotate the secret in the console and update your service.
No events for downloads by named recipientsNamed-recipient downloads are visible in the package's Activity tab and the admin Activity page. Subscribe to package.status_changed and delivery.status_changed for lifecycle events; the external_* topics cover public-link access.