Workspace Webhooks
Workspace Webhooks let a Business workspace send supported Bytes events to an external HTTPS endpoint.
They are managed under Workspace Settings → Developer API.
What you can manage
The current customer webhook surface supports:
- creating an endpoint
- editing supported endpoint settings
- pausing and reactivating delivery
- revoking an endpoint
- choosing supported Link event subscriptions
- sending a synthetic test event
- reviewing recent delivery attempts
- replaying an eligible delivery
Available event types can expand over time. Use the current Developer Docs and the event selector in Bytes as the contract for what can be subscribed to.
Signing secret
When a webhook endpoint is created or its secret is rotated, Bytes reveals the signing secret for secure storage.
Treat it like an API credential.
Do not place it in:
- browser code
- screenshots
- public repositories
- support tickets
- normal application logs
Your receiving service should verify the Bytes signature before trusting the payload.
Delivery history
Bytes keeps delivery history so you can inspect whether a request succeeded and review safe diagnostic information.
Delivery history is not a place to expose credentials, signatures or unsafe response bodies.
Replay
Replaying a delivery creates another attempt. It does not erase the original history.
Your receiving system should be idempotent so retrying the same logical event does not create duplicate business actions.
Failure does not change the Bytes source event
A failed webhook delivery does not roll back the underlying Bytes Link event.
Fix the receiving endpoint or configuration, then use the available retry/replay workflow where appropriate.
Developer reference
For signing details, event schemas and integration examples, use the Bytes Developer Docs.