POST Delivery Validation with Web-hooks

Convertr has the ability to retrospectively invalidate or validate a lead after it has been delivered to an endpoint.

They can send as many updates against a lead as they like and change between valid and invalid as they need to, however, we only have those 2 states (valid and invalid).

If the lead is flagged as Invalid, then it is no longer billable to either the publisher or the client.

It the lead is flagged as Valid, then it's billable status will be recalculated based on the current state of the publisher and campaign contract a status.

Examples as follows:

Invalidate

 POST /api/webhook/invalidate/{leadid} HTTP/1.1
 HOST: {client}.cvtr.io
 content-type: application/x-www-form-urlencoded

 Example:
 https://{enterprise}.cvtr.io/api/webhook/invalidate/[leadid]?reason=Unable to Contact&user=Danny Hannah

Validate

 POST /api/webhook/validate/{leadid} HTTP/1.1
 HOST: {client}.cvtr.io
 content-type: application/x-www-form-urlencoded

 Example:
 https://{enterprise}.cvtr.io/api/webhook/validate/[leadid]?reason=Details Confirmed&user=Danny Hannah

API Documentation

POST Delivery Validation with Web-hooks

Related content