đ Available on: Workspaces with Archive API access.
Webhooks let Archive send signed POST requests to your endpoint when new content matches a Content View, or when a bulk operation finishes. This gives your system a push-based alternative to checking the API on a timer.
Creating a Webhook Endpoint
Open Settings â Webhooks in your Archive workspace.
Click New endpoint.
Enter a descriptive Name for the receiving system.
Enter its public HTTPS address in Endpoint URL. The URL must use HTTPS, use port 443 or a port numbered 1024 or higher, contain no credentials, and respond without a redirect.
Under Events, choose what this endpoint should receive. You can select one or both:
Item added to view: fires when new content matches a Content View you select in the next step.
The operation-completed event, under Operations: fires when a bulk engagement refresh or a creator import finishes, whether it completed, partially completed, or failed. It covers the whole workspace, not a specific view.
If you selected Item added to view, go to Content views and select the views this endpoint should watch. Each selected view's filters determine which new items trigger an event.
Click Create endpoint.
đ¨ Save the signing secret immediately. Archive displays the full secret only once. Keep the whsec_ prefix â it is part of the key used to verify each delivery's X-Archive-Signature header.
If You Lose the Signing Secret
You can replace it. Open the endpoint, then choose ⯠â Rotate secretâŚ. Archive shows the new secret once, so save it right away.
For 24 hours after a rotation, Archive signs each delivery with both the new and the previous secret, so a receiver still using the old one keeps validating. After that, only the new secret works. The 24 hours run from the rotation itself, not from the next delivery.
Managing an Endpoint
The ⯠menu on the endpoint holds the rest of its actions:
Edit endpoint â change the name, the URL, or which Content views it watches.
Rotate secret⌠â replace the signing secret, as above.
Delete endpoint⌠â deliveries stop immediately and the delivery history is removed with it. Events stay in the shared event log.
Pause sits next to Send test event and stops deliveries without deleting anything. Use it while the receiving system is down.
Testing the Endpoint
Open the endpoint and click Send test event. Archive shows whether the test was delivered successfully. If it fails, confirm that the endpoint is publicly reachable over HTTPS and accepts POST requests.
Test succeeded:
Test failed:
Use the signing secret to verify the X-Archive-Signature header before processing a delivery. See the API documentation for the delivery payload and verification details.
Webhook Matching Schedule and Limits
Archive performs matching checks on a recurring schedule to find items that qualify for your webhooks:
Initial scan: When you first select a Content View for an endpoint, Archive performs one scan to match existing content. This initial scan does not trigger deliveries.
Recurring checks: After the initial scan, Archive runs matching checks approximately five minutes after content is captured and then hourly thereafter. Matching continues for a rolling 14-day window from when each item entered the workspace.
Threshold delays: If a view's filters or engagement thresholds change after content is added, it may take up to an hour for that content to reflect the new conditions and potentially trigger a new event.
Webhook and Content View limits vary by plan. Check your plan details in Settings â Webhooks for your current limits.
Monitoring Deliveries
Open an endpoint to review its Deliveries and Events tabs. Delivery history shows succeeded, failed, dropped, and pending deliveries. Event history is the reconciliation record for events that matched.
Archive keeps delivery and event history for 30 days. Failed deliveries are retried up to 8 times over 45 hours. If a delivery still fails after that, open the endpoint's Activity section to investigate. Once the receiving system is healthy, click Redeliver on that delivery to send it again.
If Archive Disables Your Endpoint
Archive automatically disables an endpoint that keeps failing. This happens when any of the following is true:
20 deliveries in a row have failed, with every retry used up.
The endpoint returns HTTP
410 Gone.Deliveries have been failing nonstop for 3 days.
You'll get an email when it happens. Archive never re-enables an endpoint on its own. Once your receiving system is fixed, open the endpoint and click Enable endpoint. You can also choose to replay the failed deliveries from the last 24 hours.
Common Questions
Can I subscribe to engagement changes?
There is no separate engagement-changed event for individual posts. To receive content, subscribe to Item added to view and use a Content View to define what your endpoint should receive. If you run bulk engagement refreshes, the operation-completed event under Operations tells you when each one finishes.
Can one item generate more than one event?
Yes. If an item matches two watched Content Views, it can generate one event for each view. It will not fire again for the same item-and-view pair.
What if I lose the signing secret?
Open the endpoint and choose Rotate secretâŚ. Save the new secret immediately; Archive displays it only once.
Where can I check a missing delivery?
Open the endpoint and review Deliveries first, then Events. Deliveries show what Archive attempted to send; Events show what matched and can be used to reconcile a missed delivery.