All webhook events include three components:

Gridio Connect uses webhooks to push real-time notifications to your system when important events occur. Instead of polling for changes, your application receives HTTP POST requests containing event data as they happen, enabling responsive integrations and keeping your systems synchronized with Gridio.

Configure your webhook endpoint and select which event types to subscribe to via the Gridio Connect API or UI. Gridio will sign each request using HMAC-SHA256 so you can verify authenticity. Your endpoint should respond with HTTP 2xx within 10 seconds; failed deliveries are retried with exponential backoff for up to 24 hours.

• event type (string)
• event timestamp (UNIX timestamp, seconds, int)
• event payload (event specific object defined below)

Customer events

Customer events notify your system when end-users are created, modified, or removed from your Gridio Connect integration. Subscribe to "customer_event" in your webhook configuration to receive these events. Use these events to keep your user database synchronized with Gridio and trigger onboarding or offboarding workflows in your application.

Customer created

Triggered when a new end-user completes the Gridio Connect onboarding flow. Use this event to provision the customer in your system, send welcome communications, or initialize their account. The ext_user_id field contains your internal identifier if you passed one during the Connect UI flow.

Sample payload

{
	"event_type": "customer.event.create",
	"timestamp": int            // UNIX timestamp, eg 1693499322,
	"payload": {
		"customer_id": uuid,      // 0197f9c1-4818-7141-9c2a-22000108e736
		"email": string           // optional, email,
		"phone_number": string,   // optionsl, +372 537-2443
		"language": string,       // EN
		"business_id": uuid,      // 0197f9c1-4818-7141-9c2a-22000108e736
		"ext_user_id": string     // "my-company-internal-id-1111999"
	}
}

Customer updated

Triggered when a customer's profile information changes, such as updated contact details or language preference. Use this to keep your local customer records synchronized with Gridio.

Sample payload

{
	"event_type": "customer.event.update",
	"timestamp": int            // UNIX timestamp, eg 1693499322,
	"payload": {
		"customer_id": uuid,      // 0197f9c1-4818-7141-9c2a-22000108e736
		"email": string           // optional, email,
		"phone_number": string,   // optional, +372 537-2443
		"language": string,       // EN
		"business_id": uuid,      // 0197f9c1-4818-7141-9c2a-22000108e736
		"ext_user_id": string     // "my-company-internal-id-1111999"
	}
}

Customer deleted

Triggered when a customer account is removed from Gridio. Use this to clean up associated records in your system, revoke access, and handle any data retention requirements.

Sample payload

{
	"event_type": "customer.event.delete",
	"timestamp": int            // UNIX timestamp, eg 1693499322,
	"payload": {
		"customer_id": uuid       // 0197f9c1-4818-7141-9c2a-22000108e736
	}
}