curl --request POST \
  --url https://app.leadconduit.com/onboard/buyer \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "invitation_id": "64b8f0f5e4b0c3a1d5e6f7a9",
  "flow_id": "64b8f0f5e4b0c3a1d5e6f7aa"
}
'

{
  "redirect": "/flows/64b8f0f5e4b0c3a1d5e6f7a8"
}

Onboards

Complete buyer delivery setup

Completes the buyer delivery setup process for a connection. This endpoint performs several operations:

Validates the connection_id or resolves it from invitation_id
Finds the seller account and their flows that deliver to this buyer
Updates or creates a buyer flow with the seller as a source
Updates seller flows with the buyer’s flow_id mapping
Sends notification emails to seller account users
Marks the connection as having buyer delivery setup complete

Note: Either connection_id or invitation_id must be provided.

Version Note:

In the first version of the onboarding modal, this endpoint is called directly by the frontend.
In the second version, this endpoint will be called automatically by the backend when the onboard status changes to completed_flows_sync.

POST

onboard

buyer

curl --request POST \
  --url https://app.leadconduit.com/onboard/buyer \
  --header 'Authorization: Basic <encoded-value>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "invitation_id": "64b8f0f5e4b0c3a1d5e6f7a9",
  "flow_id": "64b8f0f5e4b0c3a1d5e6f7aa"
}
'

{
  "redirect": "/flows/64b8f0f5e4b0c3a1d5e6f7a8"
}

Authorizations

Authorization

string

header

required

LeadConduit uses HTTP Basic Authentication with the username API and your API key as the password.

For example: API:1f1b96c9150d8050e858c043d543bb4eadae0e6f'

Body

application/json

Buyer setup request

By Connection ID
By Invitation ID

Request body for completing buyer onboarding setup. Either connection_id or invitation_id must be provided.

connection_id

string

required

The connection ID for the buyer setup

Pattern: ^[0-9a-fA-F]{24}$

Example:

"64b8f0f5e4b0c3a1d5e6f7a8"

flow_id

string

Optional. The existing flow ID to use for buyer delivery

Pattern: ^[0-9a-fA-F]{24}$

Example:

"64b8f0f5e4b0c3a1d5e6f7aa"

Response

OK - Buyer setup completed successfully

Response from the buyer onboarding endpoint

redirect

string

The URL path to redirect the user to after successful setup

Example:

"/flows/64b8f0f5e4b0c3a1d5e6f7a8"

Update an existing onboard Status

⌘I

Documentation Index

Authorizations

Body

Response