QuickRCM Public API

Build healthcare RCM integrations with tenant-safe public APIs

Use the QuickRCM public API to create and update RCM workflow records, connect partner systems, and automate operational steps across eligibility, prior authorization, claims, payment posting, denials, AR, credentialing, and related modules.

Start quickstart Open API reference Download QuickRCM OpenAPI spec

Current public API shape

Public API operations are generated from module contracts and currently use the base URL https://dev-api.quickintell.com with paths under /api/v1. Use the generated reference for exact method, path, request schema, and response schema.

What these APIs are for

The public API is intended for external services and partner integrations that automate QuickRCM workflows with Bearer API key authentication. Use the generated reference for exact request fields; callers do not need to provide tenant identifiers in public payloads.

Create local workflow records

Create or update records in QuickRCM modules such as credentialing sessions, prevention findings, AR work queues, collections, patient AR, or revenue integrity cases.

Queue or simulate controlled workflows

Some endpoints validate ownership and return queued or simulated responses instead of directly calling payer, clearinghouse, EHR, LLM, or payment systems.

Read generated contract details

The Scalar reference is generated from OpenAPI 3.1 and should be treated as the exact technical contract for each endpoint.

10-minute path

Use this sequence before drilling into individual module endpoints.

Get a public API key for one tenant

Create or request a QuickRCM public API key for your integration. The key determines tenant context and the scopes available to the request.

Send only workflow fields, not tenant selectors

Public request bodies should contain the workflow fields shown in the generated reference, such as patient, payer, claim, denial, or payment details. organizationId is not a public tenant selector.

Check route status before choosing an endpoint

Endpoint pages now show whether a route is baseline-reference, compatibility-limited, or needs publication review. Do not use compatibility routes or routes needing publication review as happy-path examples.

Use the generated reference for exact schema

Use the generated API reference for the exact method, path, request schema, response schema, status codes, and operation ID. Public API paths usually use the /api/v1 prefix.

Handle validation, authorization, rate limit, and async outcomes

Treat 400, 401, 403, 404, 409, 429, and 202 as normal integration outcomes. Queueing, dry-run, simulation, and local writes are not proof of live external execution.

Guide pages

These pages explain concepts that are hard to infer from endpoint schemas alone.

Quickstart

A short path from API key to the generated reference.