MICEtribe Event Webhooks

Receive real-time HTTP notifications when registration-related events occur on your event. Use webhooks to sync registrations with your CRM, analytics, access control, or custom backend.

Overview

Item	Details
Protocol	HTTPS POST
Content-Type	`application/json`
Delivery	Asynchronous (queued after registration events)
Timeout	10 seconds per delivery attempt
Retries	Up to 5 automatic retries for failed deliveries
Management API	Integrations service `v1` (management-authenticated)

Base URL (examples)

Environment	Base path
Staging	`https://api.staging.micetribe.com/integrations/v1`
Production	`https://api.micetribe.com/integrations/v1`

Supported triggers

Configure one or more triggers per webhook. When an event happens, we POST to your URL only if that trigger is enabled on an active webhook for the same event_id.

Trigger	Value	When it fires
Registration created	`registration.created`	A new registration is created
Registration updated	`registration.updated`	An existing registration is updated
Registration deleted	`registration.deleted`	A registration is deleted
Registration attended	`registration.attended`	Attendance is recorded
Registration printed	`registration.printed`	A badge/registration is printed

Webhook security

When you set a signing secret on the webhook, every delivery includes headers you can use to verify authenticity.

Request headers (outbound to your URL)

Header	Description
`Content-Type`	`application/json`
`Accept`	`application/json`
`X-Timestamp`	Unix timestamp (seconds) used when signing
`X-Request-Id`	Unique UUID for this delivery attempt
`X-Signature`	HMAC-SHA256 signature (only if signing secret is configured)

Signature algorithm

signature = HMAC-SHA256( secret, timestamp + "." + raw_request_body )

secret — the signing secret you configured on the webhook

timestamp — value of X-Timestamp (string)

raw_request_body — exact JSON bytes in the POST body (no re-encoding)

Compare the result (hex) to X-Signature using a constant-time comparison.

Example (PHP)

Security recommendations

Always use HTTPS for your webhook URL.

Store the signing secret securely — it is encrypted at rest in our system.

Reject old timestamps (optional) — e.g. reject if X-Timestamp is older than 5 minutes to limit replay windows.

Respond quickly — return 2xx within a few seconds; heavy work should be queued on your side.

Do not log the raw secret in your application logs.

Outbound payload format

Each delivery sends a JSON object with this structure:

{
  "registration_id": "6a08287fa219e11ac60d2a10",
  "data": {
    "registration_data": {
      "email": "attendee@example.com",
      "phone": "+97400000000",
      "fullname": "Jane Doe",
      "first_name": "Jane",
      "last_name": "Doe"
    },
    "entry_status": "Approved",
    "persona": "attendee",
    "barcode": "ABC123XY",
    "source": "online",
    "mirror": "",
    "print": {
      "print_count": 0,
      "last_printed_at": "",
      "last_printed_by": ""
    },
    "checkin": {
      "attended": false,
      "checkin_at": ""
    },
    "payment": {
      "total_payment": "10.00",
      "currency": "QAR",
      "method": "SkipCash"
    }
  },
  "meta": {
    "event_id": 7337,
    "event_name": "My Event",
    "event_slug": "my-event",
    "webhook_name": "crm-sync",
    "occurred_at": "2026-06-01T12:29:11+00:00",
    "created_at": "2026-05-18T09:27:25+00:00",
    "updated_at": "2026-06-01T08:37:39+00:00",
    "trigger": "registration.updated",
    "webhook_url": "https://your-server.com/webhooks/micetribe",
    "request_method": "post"
  }
}

Field notes

Field	Description
`registration_id`	Registration document ID
`data.registration_data`	Form field values submitted by the attendee
`data.entry_status`	Human-readable status: `Approved`, `Declined`, `Pending Approved`, `Pending Payment`, `Request Revision`, `Updated`
`data.persona`	Form/persona slug (e.g. `attendee`, `visitor`)
`data.barcode`	Registration barcode
`data.source`	`online`, `onsite`, `integrations`, or `import`
`data.print`	Included when print-related data exists
`data.checkin`	Included when check-in data exists
`data.payment`	Included when payment data exists
`data.parent`	Included when parent registration data exists
`data.product`	Included when product data exists
`meta.trigger`	Trigger that caused this delivery
`meta.webhook_name`	Name you gave the webhook in management
`meta.occurred_at`	ISO 8601 time of the underlying event

Optional blocks (print, checkin, payment, parent, product) are omitted when empty.

Delivery, logging, and retries

First delivery

A delivery log row is created per attempt (webhook_logs).

HTTP status 2xx is treated as success.

Status 300+ or network errors are treated as failure.

Automatic retries

Failed deliveries are retried by a background job (webhooks:dispatch-retries), which runs every 15 minutes and picks up rows whose next_retry_at is due.

Retry attempt	Wait before next retry
1st retry	15 minutes
2nd retry	30 minutes
3rd retry	3 hours
4th retry	6 hours
5th retry	12 hours

Maximum 5 retry attempts per log row (exponential-style backoff).

Implementing your endpoint

Minimum requirements

Accept POST with JSON body.

Return HTTP 200–299 on success.

Verify X-Signature when a signing secret is configured.

Process idempotently using registration_id + meta.trigger + X-Request-Id (retries may repeat the same payload).

Recommended response

Non-2xx responses or timeouts trigger retries.

Testing

Create a webhook pointing to webhook.site or your staging URL.

Set active: true and at least one trigger.

Perform the action on an event (create/update registration).

Confirm POST body and headers on your listener.

Verify signature with the raw body and X-Timestamp.

Troubleshooting

Issue	What to check
No webhooks received	Webhook `active` is `true`, correct `event_id`, trigger matches action
Invalid signature	Use raw request body; match `X-Timestamp` exactly; correct secret
Repeated deliveries	Retries after non-2xx; implement idempotency
Missing fields in payload	Optional blocks are omitted when empty; check trigger type
404 on management API	Use `/integrations/v1/...` (single slash after `integrations`)

Changelog (recent capabilities)

Event-level webhooks with multiple triggers per endpoint

HMAC-SHA256 signing (X-Signature, X-Timestamp)

Structured payload (registration_id, data, meta)

Delivery logging and automatic retries with backoff

Management API for CRUD on webhooks per event

Support

For management API access, webhook enablement per workspace/event, or integration questions, contact the MICEtribe integrations team.

Webhooks

MICEtribe Event Webhooks#

Overview#

Supported triggers#

Webhook security#

Request headers (outbound to your URL)#

Signature algorithm#

Example (PHP)#

Security recommendations#

Outbound payload format#

Field notes#

Delivery, logging, and retries#

First delivery#

Automatic retries#

Implementing your endpoint#

Minimum requirements#

Recommended response#

Testing#

Troubleshooting#

Changelog (recent capabilities)#

Support#