Developer tools
Valor Legacies API
Operational API, consent, webhook, and payload guidance for authorized integrations.
API overview
The agent API accepts consented lead submissions and protects operational routes with server-validated credentials. Request access rather than embedding credentials in browser code.
Read API documentationAuthentication
- Use a server-side Bearer credential issued by Valor Legacies.
- Never expose API keys in client bundles, query strings, payload previews, or logs.
- Credentials are scoped operationally and may be rotated or revoked.
Consent flow
Obtain a consent token, have the person confirm it, then submit the lead within the confirmed scope. Consent evidence is required; integrations must not manufacture or broaden consent.
Payload principles
- Collect only fields required for the requested insurance-guidance purpose.
- Redact contact data, birth dates, consent evidence, tokens, and payment details from operational logs.
- Honor DNC, opt-out, privacy, retention, and deletion controls downstream.
Operational events
lead.createdlead.reviewedlead.availablelead.purchasedlead.deliveredlead.status_updatedlead.note_addedlead.followup_setlead.appointment_createdlead.dnc_markedlead.optout_reportedagent.approvedagent.compliance_acknowledgedpayment.completedpayment.faileddispute.openedprivacy_request.openedCurrent delivery: signed lead.created webhooks are implemented when server-side target and signing configuration are present. Durable attempt logs and the remaining event deliveries are planned; this vocabulary does not claim they currently execute.
Integration support
Request access or report an integration issue without sending secrets or lead PII.
Contact integration support →