The registry as data, for the people who do this professionally
Published program rules, medication coverage, source references and review dates, with explicit unknowns where evidence is incomplete.
Free for patients using this site. API access is also free for approved uses, including organizational and commercial uses. Apply with your intended use so we can review access.
Free access, with clear responsibilities
- ✓Patients use this site for free, without an account or a paywall.
- ✓API access is free after we approve your intended use.
- ✓There are no paid API tiers. The dataset license separately permits commercial reuse with attribution.
No program pays to be listed or ranked. API access does not influence the published facts.
How to get access
-
Use the site for free
$0
Browse medications, programs, and eligibility information without an account or an API key.
Use the site -
Apply for free API access
$0
Individuals and organizations can apply by describing their intended use. We review each application before issuing a key. Every approved use is free, including commercial uses.
Request access -
Explain how you will use the data
Tell us who will use the data, where it will appear, and your expected request volume. Do not include patient information. Preserve sources, dates, review statuses, and RxAccess attribution in your integration.
There are no paid access tiers. The published dataset license is separate from API access approval.
What you get
The published program and medication data behind the site, returned as JSON. Availability of source references and individual fields varies by record.
- ·Programs: published eligibility rules, insurance tracks, and exclusions where documented.
- ·Income criteria in their published units, with explicit unknown values where a threshold is not confirmed.
- ·Medication-to-program matches, with coverage status kept separate from medication identity.
- ·Source references and review dates where available, plus each record’s publication status.
- ·The change log, so your integration can check what changed.
What you must carry through
Attribute RxAccess under CC BY 4.0. To keep your integration accurate, also display source dates and unconfirmed status with the figures; a missing value is not a denial.
A number stripped of its date becomes a claim nobody verified. An unconfirmed limit presented as verified is exactly the harm this registry exists to prevent, and it lands on a patient who stops applying.
A record’s publication status does not certify every field or every medication match.
Connect to the API
Authenticate each request
Send your key in the X-Api-Key header. Missing, invalid or revoked keys return 401.
Base path: /api/v1 on this site.
curl -H "X-Api-Key: rxk_your_key_here" \ https://www.rxaccess.org/api/v1/meta
Try a medication
curl -H "X-Api-Key: rxk_your_key_here" \ https://www.rxaccess.org/api/v1/medications/humira
Keep keys out of public repositories and shared screenshots. A key embedded in a public browser application can be read by its visitors.
Endpoints
GET /programs- All published program records
GET /programs/{slug}- One program and its published eligibility tracks
GET /medications- Published medication records, including the wider medication universe
GET /medications/{slug}- One medication and its program matches
GET /changes- The published program-change log
GET /meta- Coverage statistics and the endpoint map
The response envelope
Responses contain data and meta. This illustrative envelope omits the payload:
{
"data": [],
"meta": {
"as_of": "2026-09-05T00:00:00+00:00",
"license": "CC BY 4.0",
"attribution_required": "RxAccess - rxaccess.org",
"docs": "https://www.rxaccess.org/api"
}
}
meta.as_of is the response timestamp, not a verification date. Use each record’s review dates and source references where present. Program and medication records expose publish_gate; read coverage and individual field status separately.
Rate limits and CORS
Read requests are limited to 120 per minute per IP and 120 per minute per valid key. Exceeding a limit returns 429.
Responses send Cache-Control: private, no-store. Avoid unnecessary polling; use /changes to check published updates.
CORS permits all origins for these read endpoints. This does not make an API key safe to expose publicly.
Found a wrong value or endpoint bug? Tell us. You can also explore the registry.
Dataset license and hosted access
The published dataset is licensed under CC BY 4.0, which permits commercial reuse with attribution. Use the attribution string RxAccess - rxaccess.org. API access is free by application for approved uses. Access approval and rights to reuse the published dataset are separate.
We may revoke an API key used outside its approved use case. Revoking API access does not revoke rights already granted under CC BY 4.0 to data received under that license.
Request access
Tell us what you are building
We review each request. Tell us who will use the data, where it will appear, and whether your use is commercial.
Building an AI assistant on this?
An integration can mislead by presenting an unknown threshold as a confirmed limit, or a medication identity match as proof of assistance coverage. Keep these distinctions visible.
State the income unit and household assumptions when showing a dollar figure. Pass through not enough information rather than inventing a number or treating an unknown as ineligibility.
Read the guidance for AI assistants