# Texas House Filed Bills API

> Texas House: every bill and resolution filed this session, with authors and captions

- Vendor: `texashousefiledbillsapi` · version 1.0 · category Government Data · tags texas legislature api, texas bills api, state legislation api, texas house api, filed bills api, legislative tracking api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/texashousefiledbillsapi
- This document: https://apiclay.com/docs/texashousefiledbillsapi.md
- OpenAPI 3.1: https://apiclay.com/api/texashousefiledbillsapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `texashousefiledbillsapi`
- Updated: 2026-11-18

## About

## Texas House Filed Bills API

The filed-bills list behind the Texas House of Representatives' site: every House bill (HB), joint resolution (HJR), concurrent resolution (HCR) and simple resolution (HR) filed in the current session, each with its number, authors and caption (the one-line "Relating to ..." summary) and a link to its history on Texas Legislature Online.

Data comes from **house.texas.gov** (https://house.texas.gov). Every route calls the source's own public API and returns it unchanged.

Typical flow: `/filed-bills` once a day to follow new filings; open each `url` on capitol.texas.gov for status and text.

### Routes

#### GET `/filed-bills` - Filed bills
No parameters.

Returns: Object keyed by type (`HB`, `HJR`, `HCR`, `HR`), each an array of groups of filings with `number`, `author` (authors separated by ` | `), `caption` and `url` (history page with the `LegSess` code). About 140 KB.

### Caveats

- Covers the session currently on the House site only (special sessions included); earlier sessions are on Texas Legislature Online.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by house.texas.gov.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /filed-bills — Filed bills
- Gateway: `GET https://api.apiclay.com/v1/api/texashousefiledbillsapi/filed-bills`
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/texashousefiledbillsapi/filed-bills" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
