Real-Time XML/JSON/SOAP Post Delivery

Deliver leads as a structured document, not a form post

Some buyer systems don't accept simple form-encoded fields - they expect a structured document: an XML payload, a JSON object, or a SOAP envelope with its own headers and authentication. Real-time XML/SOAP/JSON Post delivery builds that document for every lead and sends it the moment the lead is captured or won, so you can integrate with buyers whose APIs are schema-driven without writing custom translation code.

Building the document

The same field-level transformation available on HTTP Post carries over here, applied to whichever format the buyer requires:

• Field mapping - rename a field for the target schema.
• Multi-field mapping - write one collected value into more than one field or node.
• Split fields - break a value into multiple fields, such as a phone number into area code, exchange, and line.
• Format data - reformat values, such as phone numbers or dates, to match the buyer's expected structure.
• Custom rules - remap values with a comma-separated rule, such as converting "Yes/No" to "True/False".
• Data options - send either the raw value or its label for multi-value fields.
• Conditional parameters - include or omit a tag, node, or field depending on whether it has a value, so buyers don't receive empty nodes their parser might reject.

What's different from HTTP Post

Where HTTP Post delivers simple key/value pairs, this method assembles a full XML, JSON, or SOAP document - including SOAP's header-level authentication, which many buyer systems require the username and password to be placed inside rather than passed as parameters. Connect via POST, GET, or PUT; URL-encode the payload when needed; attach static post parameters such as API keys or campaign tiers; customize posting headers; and pass lead tokens - Lead Capsule's lead ID, the vendor ID, the create timestamp, or the current time - inside the document itself.

Confirming delivery

Lead Capsule reads the buyer's response and marks a lead accepted using a static or dynamic match, the same as HTTP Post. It can also capture the buyer's own lead ID, a redirect URL to pass back to your source, a dynamic sale price, or any other custom value returned in the response - and a configurable timeout marks a lead rejected if the buyer's system doesn't respond in time.

Delivery controls

• Delivery caps - per-minute, hourly, daily, weekly, or monthly limits, including prepaid order caps.
• Exclusivity - control how long a lead stays exclusive to a buyer.
• Advanced filtering - deliver only leads matching specific field criteria, such as zip code and income.
• Scheduling - deliver within a buyer's preferred daily or hourly window.
• Lead verification - validate a lead before it's posted.
• Auto responders - notify the applicant automatically on delivery.

Delivering aged leads as structured documents

Aged inventory can move through the same XML/SOAP/JSON campaigns, with delivery throttling, a maximum batch size per send, minimum/maximum lead age controls, and a limit on how many times a lead has already been resold.