Skip to main content
Subscribe each endpoint only to the events it needs. Mobile-open resolution is not a webhook event. Use the native SDK or POST /v1/track/open response and the Mobile App analytics page instead. Bulk link operations emit one webhook event for each affected link. Biqli does not combine several links into one event envelope. Creating or changing a QR code for a link does not emit link.updated; subscribe to link events for changes to the link resource itself. Link events use this shape:
Nullable profile or configuration fields may be null.

Click object

link.clicked also includes ip. Conversion events omit ip from their click context.

Customer object

Lead and sale payloads can reference a link that was deleted after attribution. The preserved link object then includes "deleted": true, active is false, and the historical URL fields remain available.

Compatibility

Write receivers that ignore unknown fields. Biqli may add non-breaking fields in the future. Use event to choose a known parser, validate required fields your application relies on, and retain the original event ID for deduplication.