canonical: https://jentic.com/apis/healthcare.gov/healthcaregov

# Healthcare.gov Content API

The Healthcare.gov Content API exposes the public consumer-facing content on healthcare.gov as JSON, including articles, blog posts, glossary entries, FAQ questions, state-level information, and topic listings, with parallel Spanish (/es/) endpoints. Each path returns either a list resource (such as articles or topics) or a specific page by slug, in the requested media type extension. Health insurance plan-finder apps, education sites, and accessibility tools use it to surface official healthcare.gov content without scraping the website.

## For AI agents

Fetch consumer health content from healthcare.gov - articles, glossary terms, blog posts, FAQ questions, state pages, and topics - in English or Spanish.

## Scope

Does not handle plan enrollment, eligibility checks, or subsidy calculations - use for read-only fetches of healthcare.gov consumer content only.

## Capabilities

- List published articles from healthcare.gov via `/api/articles{mediaTypeExtension}`
- Retrieve glossary entries by slug through `/glossary/{pageName}{mediaTypeExtension}`
- Fetch FAQ questions and answers through `/api/questions` and `/question/{pageName}`
- Access state-by-state health insurance information via `/api/states` and `/es/{stateName}` for Spanish
- Read topic listings and blog posts through `/api/topics` and `/api/blog`
- Mirror full pages of healthcare.gov in apps via the /{pageName} endpoint family

## Use cases

### Plan-Finder Educational Content

Health insurance plan-finder apps embed healthcare.gov articles and glossary entries to explain coverage terms inline, rather than linking out and losing the user. The `/api/glossary` and `/api/articles` endpoints return curated, official content that teams can render in their own UI. The Spanish endpoints under /es/ make it straightforward to launch a bilingual experience.

Example prompt: GET `/api/articles.json` and render the title and url for the latest five articles in a sidebar

### State-Level Insurance Information Pages

Apps that route users to state-specific marketplaces use `/api/states` and /{stateName}{mediaTypeExtension} to pull the official healthcare.gov state page for a given state. This gives a current, consistent view of what each state offers without manually maintaining 50 entries. Spanish equivalents under `/es/{stateName}` are available for bilingual rollouts.

Example prompt: GET `/api/states.json` and follow the result to /{stateName}.json for a specific state to render its full page content

### FAQ and Glossary Search

Customer-support agents and chatbots search the healthcare.gov FAQ and glossary endpoints to answer common questions like what counts as a qualifying life event or how subsidies are calculated. The `/api/questions` and `/api/glossary` list endpoints provide the index, and the per-slug endpoints return the full page content for the matching item. The result is grounded answers rather than freeform text.

Example prompt: GET `/api/questions.json`, find the entry matching the user's question, and fetch `/question/{pageName}.json` for the full answer

### AI Agent Health Content via Jentic

Agents search Jentic for 'look up a health insurance term' and Jentic returns the relevant healthcare.gov glossary or article operation. The agent can then fetch grounded content for use in summaries, citations, or chat replies. Because the API is unauthenticated, no vault credentials are needed, but Jentic still wraps the call with rate-limit handling and consistent response shapes.

Example prompt: Use Jentic search 'look up a health insurance term' to load `/glossary/{pageName}.json` and execute for the slug 'premium-tax-credit'

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/articles{mediaTypeExtension}` | List articles |
| GET | `/api/blog{mediaTypeExtension}` | List blog posts |
| GET | `/api/glossary{mediaTypeExtension}` | List glossary entries |
| GET | `/api/questions{mediaTypeExtension}` | List FAQ questions |
| GET | `/api/states{mediaTypeExtension}` | List state pages |
| GET | `/api/topics{mediaTypeExtension}` | List topics |
| GET | `/glossary/{pageName}{mediaTypeExtension}` | Read a glossary entry |
| GET | `/{pageName}{mediaTypeExtension}` | Fetch a specific content page |

## Key resources

- **Articles** — Consumer articles via `/api/articles` and /{pageName}
- **Blog** — Blog posts via `/api/blog` and `/blog/{pageName}`
- **Glossary** — Glossary entries via `/api/glossary` and `/glossary/{pageName}`
- **Questions** — FAQ questions via `/api/questions` and `/question/{pageName}`
- **States** — State pages via `/api/states` and /{stateName}
- **Topics** — Topic taxonomy via `/api/topics`
- **Spanish (/es)** — Spanish-language equivalents of all content endpoints under /es/

## Why Jentic

- **Setup:** The Healthcare.gov Content API needs no credential, so wiring it by hand is mostly handling its media-type path extensions and reconciling responses with your other tools. Through Jentic you install once, import the Healthcare.gov Content API from the API Directory, and your agent calls it with a consistent request and response shape.
- **Permission scoping:** The Content API is read-only and unauthenticated, with fetches spread across endpoints like `/api/articles`, `/api/glossary`, and `/api/topics`, so limit the agent to the content fetches it needs, such as looking up an insurance term or listing articles. You choose the operations it may call, so anything outside that set is not included unless you add it.
- **Credential handling:** The Healthcare.gov Content API is unauthenticated, so there is no credential to store or inject. Jentic still routes the call through your own Jentic One instance so it shares a consistent execution surface with your other tools.
- **Discovery method:** Agents search Jentic by intent such as 'look up a health insurance term' or 'list healthcare.gov articles', and Jentic returns the matching content operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **CMS API** — CMS publishes the regulatory and provider data that underpins the consumer content on healthcare.gov
- **ClinicalTrials.gov API** — ClinicalTrials.gov provides trial-level clinical data that complements healthcare.gov's consumer guides
- **NLM API** — The National Library of Medicine APIs cover medical terminology and drug data, which healthcare.gov references in its glossary

## FAQ

### What authentication does the Healthcare.gov Content API use?

The API is fully public and does not require authentication. The spec defines no security schemes, so calls work with a plain HTTP GET and the desired media type extension.

### Can I retrieve content in Spanish?

Yes. Every content path has a Spanish equivalent under /es/, including `/es/blog/{pageName}`, `/es/glossary/{pageName}`, `/es/question/{pageName}`, and `/es/{stateName}.` Use the same media type extension as the English endpoints.

### What media types does the API return?

Each path takes a {mediaTypeExtension} segment. Append .json for JSON; the spec returns content as static JSON files served from www.healthcare.gov, so caching at the client side is straightforward.

### What are the rate limits for the Healthcare.gov Content API?

Healthcare.gov does not publish a per-IP rate limit for content endpoints, but the content is served as static JSON behind a CDN. Cache responses aggressively rather than refetching on every request.

### How do I look up a healthcare.gov glossary term through Jentic?

Search Jentic for 'look up a health insurance term', load the `/glossary/{pageName}.json` operation for healthcare.gov, and execute with the term slug. Jentic returns the title and definition for use in your reply.

### Is the Healthcare.gov Content API free?

Yes. Healthcare.gov is a US government service and the content endpoints are free to use under the public domain content guidelines published on the site.

### Can I limit what my agent is allowed to do with the Healthcare.gov Content API?

Yes. Because you run Jentic One yourself, you decide which of the Content API's read operations your agent may call, so you can allow only the fetches it needs, such as listing articles via `/api/articles` or looking up a term via `/api/glossary` and `/glossary/{pageName}`, while leaving out `/api/topics`, `/api/states`, or the blog and question endpoints. The API is read-only and unauthenticated, so there are no credentials to hand over, and any operation you do not add stays out of the agent's reach. This keeps the agent scoped to the exact content lookups your own rules permit.