Overview
The Ping-Post Request Body Tab is 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 lead fields 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 Request Body (or similar) 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.
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.
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.
Delivery errors for XML/JSON → Confirm content-type headers and payload format are acceptable to the client.
Next article: Response Settings Tab>