Create Account
Webhooks

Receive TRUXX HUB events in your own system.

Webhooks notify your application when important trip events occur. Configure each webhook endpoint from the TRUXX HUB portal, provide a secret key, and verify the signature header on every delivery.

Portal setup
Developers > WebhooksCreate and manage webhook endpoints.
Fields requiredEnter the endpoint URL, webhook name, and secret key.
Developers > Webhook LogsReview webhook delivery logs and troubleshooting history.

How to configure a webhook

  1. Open Developers > Webhooks in the TRUXX HUB portal
  2. Enter the destination URL that should receive webhook events
  3. Enter a descriptive name for the webhook
  4. Choose a secret key and save it securely in your system
  5. Use Developers > Webhook Logs to review delivery attempts and outcomes

Security model

Signature verification is recommended

TRUXX signs webhook requests using this secret. Verify the X-TRUXX-Signature (sha256=signature) header to ensure the request originated from TRUXX.

The signature is sent in the header and is based on the configured secret key. Validate the header before processing the event.

Webhook headers

{
  "X-TRUXX-Event": "trip.status_changed",
  "X-TRUXX-Event-ID": "B495A239-0F4B-4CE6-8DC6-8D558FE84D66",
  "X-TRUXX-Signature": "sha256=fe520676b1a1d93dabab2319eea03674f3632eaeeb163d1e88244f5eb1de10eb"
}
X-TRUXX-EventThe event type being delivered.
X-TRUXX-Event-IDA unique identifier for the webhook event delivery.
X-TRUXX-SignatureThe signature header your system should validate using the configured secret key.

Example payload

{
  "event": "trip.status_changed",
  "eventId": "B495A239-0F4B-4CE6-8DC6-8D558FE84D66",
  "tripId": 23217,
  "statusCode": 5,
  "statusName": "TRUXXing Now ;)"
}
eventThe webhook event name.
eventIdThe unique event identifier.
tripIdThe related TRUXX trip identifier.
statusCode / statusNameThe updated trip status values delivered with the event.

Recommended handling

  • Respond quickly after receiving the webhook request
  • Verify X-TRUXX-Signature before trusting the event
  • Log the X-TRUXX-Event-ID value to help detect duplicate deliveries
  • Use the payload event name and trip status values to update your internal state
  • Use Developers > Webhook Logs in the portal to diagnose failed deliveries