Collections

Validate or queue debt validation notice

Validates or queues local debt validation notice evidence for an organization-owned placement without external delivery.

POSTNeeds publication reviewCommunicationCollectionsoperationId: sendDebtValidationNoticehttps://dev-api.quickintell.com/api/v1/collections/placements/{placementId}/validation-notice

Needs publication reviewCommunicationPatient financials

Route status

Needs publication review

The endpoint contract is visible, but QuickRCM has not approved it yet for normal production API use.

Publication status

Needs publication review

Requires product, security/compliance, tenancy, side-effect, or module-owner approval before production public API use. Also requires E2 side-effect policy and E7 credential, webhook, and vendor trust policy before production recipes, SDK inclusion, or try-out access.

Authentication

Bearer API key declared

OpenAPI declares bearer API-key security for this operation.

Tenant context

API-key organization

API-key organization context is authoritative; request organizationId is not a public tenant selector.

Side-effect summary

Communication

May imply email, SMS, fax, phone, notices, support messages, or delivery workflow behavior.

Source artifact

docs/openapi/openapi.json

OpenAPI 3.1.0; API 1.0.0.

When to use this endpoint

Use this page as an internal baseline for the patient financials contract generated for POST /api/v1/collections/placements/{placementId}/validation-notice. External use still depends on route classification, release evidence, and endpoint-specific side-effect approval.

What this does now

Shows the generated OpenAPI shape for POST /api/v1/collections/placements/{placementId}/validation-notice, but keeps the route out of ordinary production API positioning until review is complete.

What this does not do

Does not prove external GA readiness, SDK readiness, live production execution, or complete module behavior. Mutating behavior still needs side-effect and retry evidence.

Not public from this page

Do not publish this endpoint as an ordinary developer API until its unresolved decisions are closed.

Headers and tenancy

Current headers and tenant authority. Target headers stay labeled as future until OpenAPI and release evidence declare them.

Header	Required	Current status	Notes
Authorization	Yes	Current	Bearer <QUICKRCM_API_KEY>. OpenAPI security: bearerAuth.
Idempotency-Key	No	Target/future	Do not claim universal header support until E3 and OpenAPI metadata exist.
X-Request-Id	No	Target/future	Use for support correlation only after approved; not declared as a standard OpenAPI header today.

Required scopes

Unclassified until E6 route metadata exists; do not infer scopes from route names.

Wrong-org behavior

Tenant-safe 404, empty list, or 403 is endpoint-specific and remains an evidence gap until E1 is closed.

Actor and audit

No public actor, audit, or correlation contract is published from OpenAPI alone.

Idempotency and retries

Retry behavior is documented conservatively because universal idempotency headers are not declared.

Topic	Status	Guidance
Current idempotency	Request body exposes an endpoint-specific idempotencyKey compatibility field.	Retry only with the documented key location and after checking endpoint state; 409 behavior and retention still need release evidence.
Universal header	Not declared	Do not document universal Idempotency-Key support until OpenAPI and E3 evidence declare it.
Conflict behavior	Unresolved	Same-key changed-payload, in-flight retry, fingerprint scope, and TTL behavior remain endpoint-specific evidence gaps.

Async jobs and polling

Queued work is accepted work, not proof of completed workflow execution.

Topic	Status	Guidance
Immediate response	No 202 response declared	OpenAPI does not declare HTTP 202 for this operation.
Polling and terminal states	Endpoint-specific	Use only operation-specific status endpoints visible in OpenAPI; generic job behavior, cancellation, retries, and retention are unresolved.
Later side effects	Not proven	Do not infer background execution beyond the documented response.

Files and artifacts

File-like routes need content-class, ownership, scanning, retention, and URL policy evidence before public recipes.

Topic	Status	Guidance
Content class	No file/artifact class inferred	OpenAPI text does not indicate file or artifact handling for this endpoint.
Ownership and storage keys	Not applicable unless a file field is present	Tenant ownership must be proven before retrieval or upload docs. Never expose storage keys as public identifiers.
URLs, scanning, and retention	Unresolved unless endpoint-specific evidence exists	Short-lived URLs, MIME limits, checksums, scanner status, retention, expiration, and legal hold behavior are not implied by OpenAPI examples.

Publication warnings

This endpoint needs explicit product, security/compliance, tenancy, or side-effect approval before publication.
Universal Idempotency-Key header support is not declared; retry only after checking endpoint-specific state.
External or credentialed behavior needs vendor trust, credential, webhook, and callback evidence before publication.

Related platform rules

Workflow Guide Route Status Tenant Context Errors Rate Limits PHI and Security Publication Readiness Side-Effect Modes Idempotency

Evidence

Evidence	Status	Caveat
OpenAPI artifact	docs/openapi/openapi.json; OpenAPI 3.1.0; API 1.0.0.	Generated baseline contract only.
Route registry	Needs publication review from documentation classification overlay.	E6 route registry evidence is still required before external publication.
Example validation	Generated examples are internal baseline aids.	No external publication claim; examples must pass no-PHI/no-secret/no-raw-payload/no-storage-key checks.
Last reviewed	Implementation run 20260619T-docs-impl; source boardroom packet 20260619T064820Z.	Refresh this evidence for release workspaces.
Release evidence	E9 required.	No SDK readiness, production readiness, or expanded external docs claim from this endpoint page.

Collections public API.

Collections APIs expose organization-scoped collection agency configuration, local bad debt placement tracking, recovery posting, placement dispute notes, safe debt validation notice simulation or queue evidence, and collections compliance rule/check workflows. The bearer API key selects the organization. Public callers should not send an `organizationId` tenant selector. The public handlers enforce organization scope when looking up collection agencies, bad debt placements, and compliance rules. For caller-supplied `patientId`, `patientAccountId`, and `claimIds` in placement creation, callers should use identifiers from the same authenticated organization; the public placement create endpoint stores those local references and does not document full referential validation for every supplied patient, account, or claim. For compliance checks, an optional `placementId` is used only for organization-scoped enrichment when found. These endpoints manage QuickRCM local workflow state and audit evidence. They do not by themselves transmit debt to an external agency, send mail, email, or SMS, collect payment, post cash, update payer systems, or create legal compliance guarantees. Use synthetic examples only, and keep request notes free of Protected Health Information (PHI), credentials, tokens, raw Electronic Data Interchange (EDI), transcripts, S3 keys, payer portal credentials, payment card details, and vendor payloads. Compliance language should expand Telephone Consumer Protection Act (TCPA) and Fair Debt Collection Practices Act (FDCPA) on first use and avoid presenting local checks as legal advice.

What this endpoint does

Use case

Use this when an integration needs a safe simulation or local queue marker before any regulated debt validation communication workflow.

Before calling

Authenticate with `collections:write` and resolve `placementId` from the same tenant. Choose `dryRun` for simulation or `queueOnly` for local queue evidence.

Request and response behavior

Request guidance

`method` defaults to `mail` and must be `mail`, `email`, or `sms`. `dryRun` defaults to true. `queueOnly` defaults to false. Requests where both `dryRun` and `queueOnly` are false are rejected. If both `dryRun` and `queueOnly` are true, dry-run behavior wins and the response status remains `SIMULATED_ONLY`; only `queueOnly: true` with `dryRun: false` appends local queue evidence. `idempotencyKey` is accepted but no server-side replay/deduplication behavior is evidenced.

Use dry-run mode for validation-only requests.
Use `queueOnly: true` and `dryRun: false` only when local queue evidence should be recorded.
Do not claim external mail, email, or SMS delivery from this response.
Do not put Protected Health Information (PHI) or credentials in `idempotencyKey`.

Response semantics

The response returns `placementId`, status `SIMULATED_ONLY` or `QUEUED`, `externalDelivery: NOT_SENT`, method, dryRun, and queueOnly. It does not send mail, email, SMS, or agency portal messages.

`externalDelivery` is always `NOT_SENT` in the public response schema.
`QUEUED` means local queue evidence only.
`SIMULATED_ONLY` means no local queue note was written by this public handler.

Errors and retries

Fix invalid mode combinations before retrying. Treat 404 as missing or wrong-organization placement. Queue-only requests mutate placement notes, so re-read after timeouts before retrying.

400 can indicate both `dryRun` and `queueOnly` are false.
404 can indicate the placement is not visible to the authenticated organization.

Template boundary before examples

The route class, authentication state, tenancy rule, side-effect mode, idempotency status, async behavior, file policy, warnings, links, and evidence above are part of the endpoint contract. Treat generated examples below as internal baseline aids until release evidence closes.

Path parameters

Name	Location	Required	Type	Description	Validation and safety notes
placementId	path	Yes	string	QuickRCM bad debt placement identifier. Placement read/write handlers look it up inside the organization selected by the bearer API key.	Minimum length: 1. Sensitive credential or storage-adjacent value; use placeholders only.

Query parameters

This endpoint does not define query parameters.

OpenAPI-declared header parameters

Standard platform header guidance appears in the governance panel. This table only lists operation-specific headers declared in OpenAPI.

This endpoint does not define operation-specific header parameters.

Request body

JSON fields from the generated OpenAPI schema with pilot enrichment applied where available. Nested object fields are shown with dotted paths.

Name	Location	Required	Type	Description	Validation and safety notes
method	body	No	mail \| email \| sms	Requested notice channel enum: `mail`, `email`, or `sms`; defaults to `mail`.	Enum values are declared in the Type column. Default: mail. Potential PHI; use synthetic examples and avoid logging raw values.
dryRun	body	No	boolean	Safe simulation flag. Defaults to true and takes precedence when true.	Default: true.
queueOnly	body	No	boolean	Local queue-evidence flag. Defaults to false; only queues when true and `dryRun` is false.	Default: false.
idempotencyKey	body	No	string	Optional caller retry marker capped at 120 characters. Current evidence does not show server-side deduplication.	Minimum length: 1. Maximum length: 120. Endpoint-specific compatibility key; universal Idempotency-Key header support is not declared.

Generated request example

Generated examples are baseline contract aids only. They are not external publication evidence and must not include real PHI, credentials, raw vendor payloads, raw EDI, transcripts, storage keys, or signed URLs.

{
  "method": "mail",
  "dryRun": true,
  "queueOnly": false,
  "idempotencyKey": "example-idempotencykey"
}

Successful responses

Generated response examples show the baseline OpenAPI contract. Tenant identifier echo, PHI redaction, pagination, money, date/time, and enum semantics remain endpoint-specific publication checks.

200

Validation notice request accepted safely

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "placementId": "00000000-0000-4000-8000-000000000001",
    "status": "SIMULATED_ONLY",
    "externalDelivery": "NOT_SENT",
    "method": "mail",
    "dryRun": true,
    "queueOnly": true
  }
}

Error responses

Errors must remain sanitized. Do not include raw payer, EHR, SFTP, SMTP, Stripe, LLM/OCR, browser automation, file, transcript, EDI, worker, or vendor payloads.

400

Invalid request