Skip to main content
POST
Submit feedback for a lead using your own record ID

Path Parameters

recipient_name
string
required

The name of the inbound feedback integration that will parse the request, for example standard.

Example:

"standard"

Body

The feedback to record for the lead, in the format the named integration expects. The standard format is documented here.

The feedback payload a recipient sends about a delivered lead. The same fields apply whether the body is JSON, XML (wrapped in a <feedback> root element), or form encoded, and whether they are sent in the body of a POST or the query string of a GET.

type
enum<string>
required

The kind of feedback. Use conversion when the lead progressed to a lifecycle stage, or return when the lead is being given back.

Available options:
conversion,
return
recipient_record_id
string
required

The ID under which you stored the lead in your own system, as sent with the lead when it was delivered.

Example:

"54321"

reason
string

For a conversion, the name of the lifecycle stage the lead reached (for example Appointment Set or Sale Closed). For a return, the reason the lead is being returned (for example Wrong number).

Optional. A submission without a reason is accepted, but the reason is what the step's acceptance criteria are usually written against, so omitting it will often cause the feedback to be rejected with outcome: "failure".

Example:

"Sale Closed"

occurred_at
string

When the status actually changed in your system, as an ISO 8601 timestamp. Optional; when omitted, LeadConduit stamps the feedback with the time it was received. Use this when feedback is sent in batches, so the lifecycle date reflects the CRM event rather than the upload.

Timezone-naive values (2026-05-30T08:00:00) and date-only values (2026-05-30) are read as UTC. A value that cannot be parsed as ISO 8601 is ignored — the feedback is still accepted, LeadConduit falls back to receipt time, and an occurred_at_warning variable is recorded on the feedback-received event so the misconfiguration is visible in the event log.

Example:

"2026-05-30T08:00:00Z"

Response

The feedback submission was processed. Check outcome to see whether it was accepted.

The result of a feedback submission. Returned as JSON by default, or as XML (wrapped in a <result> root element) when requested via the Accept header.

outcome
enum<string>

Whether the feedback was accepted. Check this field rather than the status code — a rejected submission is still reported with 201.

Available options:
success,
failure,
error
Example:

"success"

reason
string | null

The reason the feedback was not recorded, when the outcome is not success.

price
number

The price paid to the recipient for the lead. Present only when the delivery step priced the lead.

lead
object

Identifying details of the lead the feedback applies to.