Any HTTPS receiver you run
Your HTTPS endpoints
Any service that can receive an HTTPS POST and check an HMAC signature can follow changes in Chorus.
An org:admin registers the endpoint URL and the events it wants. Chorus posts each event as JSON with the X-DNS-Signature header; your receiver recomputes the HMAC-SHA256 over the timestamp and raw body with the signing secret and compares.
Deliveries are at least once, so receivers should be idempotent. Chorus refuses private and internal addresses as targets.
More integrations
All integrations →- 01
Zitadel
People sign in through Zitadel, the identity provider shared across the Fleetworks suite.
- 02
Expo push notifications
When a webhook delivery is dead-lettered, Chorus sends a push through Expo to the organization’s registered devices.
- 03
Yellow Pages
A record may point at a YellowPages service by id, so you can tell which service a record belongs to.