Partner lead webhook event

A partner organization's lead webhook sends one event, contact_request_created, each time a new lead is created on a profile the organization owns. This page describes that payload. For headers, the signature check and how to reply, see Verify and handle webhook deliveries.

Directory owners receive a different, larger payload under the same event name. That one is described in Directory webhook events and payloads.

When it is sent

One delivery for every new lead on any profile the organization owns, however it was created:

a visitor submits the contact form on the partner's profile

the directory's team assigns a matchmaking request to the partner

the directory owner creates the lead through the API

It is not sent when a lead changes later (accepted, declined, status updates). It is not sent for a directory whose owner has switched partner lead delivery off; it is on by default.

Setting it up

A partner adds the webhook in the PartnerPage dashboard under Settings, then Developers, on the Lead webhook card. Each organization has one webhook and its own signing secret. The step-by-step guide is in the Help Center: Send new leads to your own tools with a webhook.

The URL must:

start with https://

resolve to a public address (not localhost, .local, .internal or a private network)

not contain a username or password

be at most 255 characters

be the final address: redirects are not followed

Payload

Field	Meaning
`entry_id`	Id of the partner profile that received the lead
`directory_id`	Id of the directory it came from
`organization_id`	The partner organization's id, the same Organization ID shown on the Developers page
`contact_request.id`	Lead id
`contact_request.created`	When the lead was created, in UTC, formatted `YYYY-MM-DD HH:MM`
`contact_request.state`	`pending` for a new lead
`contact_request.project_status`	`null` for a new lead
`contact_request.first_name`, `last_name`, `email`, `phone`	The lead's contact details
`contact_request.company_name`, `company_website`	The lead's company
`contact_request.comments`	The message the lead wrote
`contact_request.utm_query_params`	UTM parameters captured on the page, or `null`
`contact_request.source`	`contact_request` (submitted on the profile) or `matchmaking` (assigned from a matchmaking request)
`contact_request.decline_reason`, `decline_reason_detail`	`null` for a new lead
`contact_request.entry`	The profile: `id`, `title` and `owner` (the partner organization's id)
`contact_request.directory`	The directory: `id` and `name`
`custom_fields`	Answers to the directory's custom form questions. Each item has `export_label`, `internal_label` and `text_value`
`partner_contact_request_url`	Link to the lead in the partner's PartnerPage dashboard

{
  "entry_id": "10c83cb2-ec23-49c5-b1c1-36ad2c5f5744",
  "directory_id": "a6736e4f-ad5b-4cc9-856b-9f3bf6688a79",
  "organization_id": "6ba56da9-a8ae-4d84-9337-cedabefdcdc6",
  "contact_request": {
    "id": "58e8eba8-ce91-4ab7-870a-0c33108b7101",
    "created": "2026-10-05 16:19",
    "state": "pending",
    "project_status": null,
    "first_name": "Jon",
    "last_name": "Smith",
    "email": "jon.smith@example.com",
    "phone": "8322787786",
    "company_name": "Example Manufacturing",
    "company_website": "https://www.example.com/",
    "comments": "We need help rolling out the product to 200 users.",
    "utm_query_params": null,
    "source": "contact_request",
    "decline_reason": null,
    "decline_reason_detail": null,
    "entry": {
      "id": "10c83cb2-ec23-49c5-b1c1-36ad2c5f5744",
      "title": "Northwind Consulting",
      "owner": "6ba56da9-a8ae-4d84-9337-cedabefdcdc6"
    },
    "directory": {
      "id": "a6736e4f-ad5b-4cc9-856b-9f3bf6688a79",
      "name": "Acme Partner Directory"
    }
  },
  "custom_fields": [
    {
      "export_label": "Desired timeline",
      "internal_label": "desired_timeline",
      "text_value": "Q2"
    }
  ],
  "partner_contact_request_url": "https://directory.partnerpage.io/profiles/solutions/a6736e4f-ad5b-4cc9-856b-9f3bf6688a79/partner/10c83cb2-ec23-49c5-b1c1-36ad2c5f5744/contact-requests/58e8eba8-ce91-4ab7-870a-0c33108b7101"
}

Differences from the directory owner's payload

If you build one receiver for both kinds of webhook, note what the partner payload leaves out. It carries what the partner sees on the lead in their dashboard, and nothing the directory owner keeps to itself.

Directory owner's payload	Partner payload
`directory_contact_request_url` (link into the owner's dashboard)	Replaced by `partner_contact_request_url`
`contact_request.directory` with `org_id`, `org_name`, `contact_request_project_statuses_enabled`	Only `id` and `name`
`terms`, `privacy`, `share`	Not included
`custom_form_response_id`, `match_origin`, `routing_source`, `legacy_filter_responses`	Not included
`close_reason`, `close_reason_detail`	Not included
No `organization_id` at the top level	`organization_id` included

When it is sent#

Setting it up#

Payload#

Differences from the directory owner's payload#

When it is sent

Setting it up

Payload

Differences from the directory owner's payload