Contract Validation Endpoint

if your integration is part of a ci/cd system, you can use this contract validation api to ensure jomablue is continuing to produce payloads as expected this validation and formatting logic applied to this api is the same that formats and produces the sns messages in our push api it is also the same validation that is used through jomablue's automated test suites the result being a consistent and reliable output that can be tested against by your systems overview this api is turned on per jomablue instance we will advise if it has been enabled for your instance the contract validation api endpoint is as follows endpoint integration/api/validate/payload method post authentication none headers content type application/json accept application/json the responses you'll receive back from the api are as follows http status code meaning 200 success 403 contract api is not available on this instance 422 request did not pass validation request specification a single endpoint will be provided where both ‘events’, ‘people’ 'session participation' and 'lead' requests can be made the resource type differentiates the different request body requirements all keys are required as part of the payload, however their values may be empty if the specification allows for request body specification, please refer to the sample payloads under the relevant payload documentation pages the payloads produced for sns messages are the same as required for the endpoint