Developers
API referenceBusiness sign in

Claims

Attach a photo or document

POST/claims/{claimId}/evidence

Scope claims.writeLIVE keys only

JPEG, PNG or PDF up to 3.5 MB, up to 10 files, before the decision. Stored privately; the same file twice returns 409.

Request

Path parameters

Path parameters
NameInTypeDescription
claimIdRequiredpathstringPattern ^(?:QD-CLM-[A-F0-9]{24}|QDCLM[A-Z0-9]{3,31})$

Body ClaimEvidenceRequest

Request body
FieldTypeDescription
fileNameRequiredstring0–200 characters
contentBase64RequiredstringThe file, base64 encoded: JPEG, PNG or PDF, up to 3.5 MB.

Response

Success responses
StatusMeaning
201Attached

The body is { "status": "success", "data": … }. Fields of data (ClaimEvidenceResult):

Response data
FieldTypeDescription
evidenceRequiredClaimEvidence

Errors

Errors use the error envelope { "status": "error", "message", "code"?, "details"? }.

Error responses
StatusWhen
400The request is not valid. A field is missing or invalid, or the Idempotency-Key header is missing or malformed.
401Missing, invalid, expired or revoked API key. The API key is missing, invalid, expired or revoked.
403The key lacks the scope, or the operation needs a LIVE key. The key lacks the scope, or this call needs a LIVE key (LIVE_KEY_REQUIRED), or the Business owner is not verified (SENDER_VERIFICATION_REQUIRED).
404Not found for this Business and environment. IDs from another Business or environment are always 404. Not found for this Business and environment. IDs from another Business or the other environment are always 404.
409Idempotency key reused with another body, or the resource changed state. The idempotency key was used with a different body, a reference is already taken, or the resource changed state.
429Too many requests. See the RateLimit headers. Too many requests. Wait for Retry-After, then retry with the same idempotency key.