Sign in
Start free7-day free trial
Live API contract
API REFERENCE / Waiver records

Download a signed waiver PDF

GET/v1/waivers/{id}/pdf

The rendered waiver as application/pdf. 404 until the render has finished (pdfStatus: "ready"). poll GET /v1/waivers/{id}, or wait for the waiver.signed webhook and retry. Every download is recorded in both the audit log and the PHI access log.

Authentication

Send an organization-scoped API key in the Authorization header. Keep credentials on your server.

waivers:read
Authentication and API keys →

Parameters

idpathrequired
string · uuid

Responses

404 Response schema

application/json

errorobjectrequired
View nested fields
codestringrequired
messagestringrequired
requestIdstringrequired
detailsvalue
View complete response schema
HTTP 404 schema
{
  "type": "object",
  "properties": {
    "error": {
      "type": "object",
      "properties": {
        "code": {
          "type": "string"
        },
        "message": {
          "type": "string"
        },
        "requestId": {
          "type": "string"
        },
        "details": {}
      },
      "required": [
        "code",
        "message",
        "requestId"
      ],
      "additionalProperties": false
    }
  },
  "required": [
    "error"
  ],
  "additionalProperties": false
}

A successful response is a binary PDF with an application/pdf content type. The contract also documents the unavailable-file response. Wait until the record reports a ready PDF before downloading.

Authentication and validation failures use the shared error envelope. Save the request ID when diagnosing a failed call.

Build the surrounding workflow

Read the waiver records guide for ordering, verification and recovery. Browse the other waiver records endpoints when you need the next operation.