Overview
The Ping-Post Request Body Tabs are where you configure the JSON or XML schema that will be used when sending the ping request to your client’s system. This defines the payload structure and allows you to map your lead fields, system fields, eval functions, etc., into the schema so the client receives the data they expect.
Key Functionality
Accepts JSON or XML schemas based on client requirements
Enables insertion of delivery method tags (placeholders) corresponding to lead fields
Supports auto-population of field values during delivery
Works in tandem with field mappings to ensure accurate data delivery
How to Use This Feature
Navigate to the PING Configuration Request Body tab in your Ping-Post delivery method setup.
Input the JSON or XML schema as defined in your client’s posting documentation.
Within the schema, use dropdowns (or tag pickers) to insert delivery method tags that map to lead fields.
At runtime, those tags are replaced with actual lead field values for each lead.
Save the configuration once your schema is complete and mappings are correct.
Replicate in the POST Configuration Request Body tab, including all the fields per your client's posting instructions.
Best Practices
Always refer to the client’s technical documentation for the required schema structure.
Use dropdown/tag insertions rather than manual typing to minimize errors.
Keep the schema as lean as possible; only include the necessary fields.
Test with sample lead data in a sandbox environment to validate that the schema works properly.- Verify client endpoint requirements to ensure all necessary fields are included in the lead submission.
Implement validation checks to ensure required fields, such as IP addresses or transaction IDs, are present before submission.
Troubleshooting
Payload rejected by client → Confirm the schema matches exactly (tags, brackets, field names).
Tags not substituted → Ensure the tag names match your lead fields and that you used the tag picker.
Incorrect or missing data in payload → Check your field mappings and tag assignments. Remember that Ping payloads will always include partial information, and once accepted by your client, the system will send the Post payload with full information.
Delivery errors for XML/JSON → Confirm content-type headers and payload format are acceptable to the client.
Missing required property errors → For example, if the error states 'must have required property
ip_addressat path: /contact,' ensure that the IP address or other required fields are included in the lead submission.Transaction ID cannot be found → Verify that the transaction ID is correctly implemented and mapped per the client’s posting instructions and that there is a confirmed buyer for the lead.
Next article: Response Settings Tab>