Overview
Webhooks allow your application to receive real-time HTTP notifications when events occur in FieldWise. Instead of polling the API, webhooks push data to your endpoint instantly.Supported Events
| Event | Description |
|---|---|
document.processing.started | Document processing has begun |
document.processing.completed | Document processed successfully |
document.processing.failed | Document processing failed |
Webhook Payload
Payload Fields
| Field | Type | Description |
|---|---|---|
event | string | Event type (dot-notation) |
timestamp | string | ISO 8601 timestamp |
data.task_identifier | string | Unique task ID for tracking |
data.document_id | integer | null | Document ID (available on completion) |
data.external_id | string | null | Your custom reference ID |
data.status | string | processing, completed, or failed |
data.message | string | Human-readable status description |
data.file_name | string | Original file name |
Security Headers
Every webhook includes these headers:| Header | Description |
|---|---|
X-FieldWise-Signature | HMAC-SHA256 signature |
X-FieldWise-Timestamp | Timestamp used in signature |
X-FieldWise-Event | Event type |
Signature Verification
Always verify webhook signatures to ensure requests come from FieldWise.Retry Policy
Failed deliveries are automatically retried:| Attempt | Delay |
|---|---|
| 1st retry | 30 seconds |
| 2nd retry | 60 seconds |
| 3rd retry | 120 seconds |
Best Practices
Respond Quickly
Return
200 OK immediately, then process asynchronously. Timeout is 30 seconds.Handle Duplicates
Use
task_identifier to deduplicate. Webhooks may be delivered more than once.Use HTTPS
Always use HTTPS endpoints in production to protect webhook payloads.
Verify Signatures
Always verify the
X-FieldWise-Signature header before processing.Managing Webhooks
Configure webhooks directly in the FieldWise dashboard under Settings → Webhooks. From there you can:- Create new webhooks
- Edit webhook settings
- Delete webhooks
- Send test payloads
- Rotate secrets