partner.merged

Occurs when two partner accounts are merged.

Tip

When two partner accounts are merged, the sourcePartner account is collapsed into the targetPartner account. The source partner's enrollment in the program no longer exists after the merge, so any future API calls or webhook events for this partner will reference targetPartner.id instead.

If you store partner IDs in your own system, listen to this webhook to update your records to use the targetPartner.id.

Response body parameters

All webhook payloads follow a consistent top-level structure with event-specific data nested within the data object.

idstring#

The event ID.

eventstring#

The event type that triggered the webhook (e.g., partner.merged).

createdAtstring#

ISO 8601 timestamp when the webhook event was created.

dataobject#

Event-specific data containing detailed information about the event. The data object for the partner.merged event contains the following parameters:

Show object parameters

sourcePartnerobject#

The source partner account that was merged away. Its enrollment in this program no longer exists; use targetPartner.id instead.

Show sourcePartner object

idstring#

The partner's unique ID on Dub.

tenantIdstring | null#

The partner's unique ID in your system.

emailstring | null#

The partner's email address.

targetPartnerobject#

The target partner account that the source account was merged into.

Show targetPartner object

idstring#

The partner's unique ID on Dub.

tenantIdstring | null#

The partner's unique ID in your system.

emailstring | null#

The partner's email address.

targetAlreadyEnrolledboolean#

Whether the target partner account was already enrolled in this program before the merge.

If true, both partners were already enrolled in the program and the merge process collapsed the source account into the target account.

If false, only the source partner account was enrolled in the program, which means the partner's ID in your program was updated to the target partner's ID.