Compliance requests

A compliance request is HoundDog asking a party for insurance documents: it is created when a party needs a certificate, carries the reminder cadence, and completes when the party becomes compliant. Requests are created and completed by the compliance engine; the API reads them. To remind a party, use POST /parties/:id/send_reminder.

Operation	Scope
`GET /parties/:id/compliance_requests`	`read`
`GET /compliance_requests/:id`	`read`

The compliance request entity

{
  "id": 88120,
  "party_id": 191537,
  "project_id": null,
  "completed": false,
  "completed_at": null,
  "unresponsive": false,
  "email_request_count": 2,
  "email_last_sent": "2026-10-04T14:00:00Z",
  "sms_request_count": 0,
  "sms_last_sent": null,
  "review_needed": false,
  "review_failed": false,
  "agent": {
    "entered": true,
    "parallel": false,
    "name": "Pat Lee",
    "email": "[email protected]",
    "phone": "555-0199",
    "email_request_count": 1,
    "email_last_sent": "2026-10-05T14:00:00Z",
    "source": null
  },
  "upload_url": "https://app.hounddog.com/upload-certificate/9b1f...",
  "created_at": "2026-10-01T15:02:11Z",
  "updated_at": "2026-10-05T14:00:00Z"
}

Field	Meaning
`completed`, `completed_at`	The request is closed (the party became compliant, was archived, or the request was replaced)
`unresponsive`	Every reminder went out without a response
`email_request_count`, `email_last_sent`	The party-side cadence (on an account that sends text messages, a reminder text sent on a cycle advances the same count and clock; `sms_request_count` and `sms_last_sent` are served for compatibility and are always 0 and `null`). The account's follow-up settings decide the delay between reminders and their number
`review_needed`, `review_failed`	Manual review state of the submission
`agent`	The insurance agent leg: `entered` when the party handed the request to its agent, `parallel` when the agent is contacted alongside the party from creation, the agent's contact details, its own counters, and `source` (where a parallel leg's address came from)
`upload_url`	The party's upload page for this request, the same link the party's insurance entries in outreach show. Anyone with this link can submit documents for the party, so treat it like a password, share it only with the party, and never log it

Fields of features your account does not use are present with an empty value.

Who each open request is asking, and how far each person's reminders have gone, is on the party: see Outreach.

GET /parties/:id/compliance_requests

The party's requests, newest first, completed ones included, in the collection envelope.

GET /compliance_requests/:id

One request. 404 for another account's request. Also 404 for a request of one of your individuals.