Webhooks in Device Rescue allow your account to automatically receive real-time event notifications and forward them to external systems such as internal databases, apps, or automations that accept JSON payloads.
🔒 Only Admin users can create and manage Webhook subscriptions.
How to Subscribe to a Webhook
-
Go to Account Settings → Webhooks & API → Webhook Endpoints
-
Click Add Webhook Endpoint
-
Enter your Webhook URL (must be an HTTPS endpoint ready to accept POST requests)
-
Select the Webhook Environment:
-
Test – For testing and development environments
-
Production – For live, production webhooks triggered by real account activities
-
-
Click Create Webhook
Once created, your webhook will immediately be ready to receive event payloads based on the environment selected.
Webhook Secrets (Optional but Recommended)
When a webhook is created, Device Rescue also generates a Webhook Secret:
-
The Secret is optional, but highly recommended for added security
-
You can use the Secret to validate incoming webhook payloads on your server
-
This ensures that payloads received by your endpoint are genuinely coming from Device Rescue and not a third party
🛡️ Tip: Your server should verify the secret for every webhook event it receives.
You can view, copy, or reset the Webhook Secret at any time from the Webhook details screen.
What Webhooks Send
Each webhook event includes:
-
Event Type (example:
asset.assignment.created,asset.updated,retrieval.created) -
Timestamp
-
JSON Payload containing the associated object data
Best Practices
-
Use HTTPS for your Webhook URL
-
Validate the webhook secret on your endpoint for security
-
Ensure your endpoint returns an HTTP 2XX status code to acknowledge successful receipt
-
Use separate Webhook Endpoints for Test and Production environments
📢 Note: Test and Production webhooks are fully isolated to avoid cross-environment confusion.