HPH Integrations APIv1 · Customer Testing
Customer Testing. Available to the Customer Testing group. Production is not available.
Developer guide

Errors, concealment, and support

Handle stable problem responses without relying on internal implementation detail.

Problem response contract

Error responses use application/problem+json with the fields type, title, status, code, correlation_id, retryable, and errors. Like every other body, field names are snake_case. Branch on the documented HTTP status and stable code, retain correlation_id for support, and do not parse title text as a machine contract.

Safe support escalation

Provide the correlation_id from the problem or successful response, the UTC timestamp, operation name, HTTP status, and stable problem code through your HPH support contact. Do not send credentials, idempotency keys, candidate tokens, complete item bodies, or complete responses.

Disclosure boundary

Responses contain only fields defined by the public response contract and permitted for the represented Company. They omit confidential matching evidence, exact scores or thresholds, credentials, and implementation details. A concealed response must not be used to infer company, application, operation, or candidate existence.