link.updated

Biqli sends link.updated when a tracked link field changes, including its name, destination URL, key, description, expiration, active state, domain, password state, or UTM configuration. The payload contains the complete link after the update. It is not a before-and-after diff. Password values and UTM configuration are intentionally not included in the webhook link object. An update to one of those settings can therefore produce a notification whose exposed link fields look unchanged. Use this event as a synchronization signal, not as an audit diff.

Example payload

{
  "id": "evt_01m2exampleupdated0000000000",
  "event": "link.updated",
  "createdAt": "2026-09-14T14:05:00+00:00",
  "data": {
    "id": "biq_lnk_01M2EXAMPLE00000000000000",
    "externalId": "campaign_1842",
    "name": "Autumn campaign",
    "url": "https://example.com/autumn-sale",
    "shortUrl": "https://go.example.com/autumn-sale",
    "key": "autumn-sale",
    "description": "Updated autumn launch",
    "active": true,
    "expiresAt": "2026-12-01T00:00:00+00:00",
    "workspaceId": "biq_ws_01M2EXAMPLE000000000000000",
    "createdAt": "2026-09-14T13:40:23+00:00",
    "updatedAt": "2026-09-14T14:04:59+00:00"
  }
}

Recommended handling

Upsert your local record by data.id and replace its synchronized fields with the values in data. Do not infer which field changed by comparing webhook arrival order: different events are not guaranteed to arrive in order. Deduplicate processing with the envelope id.

GETTING STARTED

EVENTS

link.updated

Example payload

Recommended handling

​Example payload

​Recommended handling

Example payload

Recommended handling