Quick reference

Subscribe to receive connection events when creating your webhook. The default event is connection.accepted; connection.new is opt-in and must be named explicitly:

curl -X POST https://api.curviate.com/v1/webhooks \
  -H "Authorization: Bearer cvt_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "source": "user",
    "request_url": "https://hooks.example.com/curviate",
    "account_ids": ["acc_YOUR_ACCOUNT_ID"],
    "events": ["connection.accepted"]
  }'

connection.accepted

Fired when a pending connection invitation sent from a connected account is accepted by the recipient. Once received, the two members are connected and messaging is available without InMail credits.

{
  "id":          "wdl_YOUR_DELIVERY_ID",
  "webhook_id":  "wh_YOUR_WEBHOOK_ID",
  "event":       "connection.accepted",
  "data": {
    "account_id": "acc_YOUR_ACCOUNT_ID",
    "event":       "connection.accepted",
    "user": {
      "full_name":         "Alex Jordan",
      "provider_id":       "urn:li:member:123456789",
      "public_identifier": "alexjordan",
      "profile_url":       "https://www.linkedin.com/in/alexjordan",
      "picture_url":       "https://media.licdn.com/dms/image/example/photo.jpg"
    },
    "occurred_at": "2026-05-28T16:45:00.000Z"
  },
  "delivered_at": "2026-05-29T00:45:01.012Z"
}

Notable fields

• data.user.full_name, the new connection's display name on LinkedIn.
• data.user.provider_id, the LinkedIn member URN (e.g. urn:li:member:123456789).
• data.user.public_identifier, the LinkedIn vanity URL slug (e.g. alexjordan from linkedin.com/in/alexjordan).
• data.user.profile_url, direct link to the connection's public profile.
• data.user.picture_url, profile photo URL; may be absent when the member has no public photo.
• data.occurred_at, when the connection was formed on LinkedIn. Due to the polling constraint, delivered_at may be significantly later than occurred_at.

connection.new

Fired when any new relation appears on the connected account, any new LinkedIn connection, not just ones you invited. It is a superset of connection.accepted. connection.new is opt-in, name it in events[] to receive it.

connection.new delivers the same data shape as connection.accepted. data.account_id is always present, sourced from the delivery, so scope your handler on it.

{
  "id":          "wdl_YOUR_DELIVERY_ID",
  "webhook_id":  "wh_YOUR_WEBHOOK_ID",
  "event":       "connection.new",
  "data": {
    "account_id": "acc_YOUR_ACCOUNT_ID",
    "event":       "connection.new",
    "user": {
      "full_name":         "Sam Rivera",
      "provider_id":       "urn:li:member:246813579",
      "public_identifier": "samrivera",
      "profile_url":       "https://www.linkedin.com/in/samrivera",
      "picture_url":       "https://media.licdn.com/dms/image/example/photo.jpg"
    },
    "occurred_at": "2026-05-28T18:00:00.000Z"
  },
  "delivered_at": "2026-05-28T22:00:01.500Z"
}

Tracking new followers

Field remapping

Unlike the messaging source, user validates the array against a closed enum, so a key outside the five below fails at create time with 400 INVALID_REQUEST naming the accepted values.

user_provider_id        user_full_name        user_public_identifier
user_profile_url        user_picture_url

Those five are the whole set. account_id, account_type, webhook_name, and timestamp are not accepted here, whatever a messaging-source example may suggest.

When data is omitted the default payload shape documented above is delivered.

Errors you may hit

Full envelope shapes are in the error reference.

Next steps

• Verifying signatures: validate every delivery before you process it.
• Delivery and retries: the retry schedule and endpoint health.
• Messaging events: message and chat payloads.
• Account status events: account lifecycle payloads.