Texas APIhouse.texas.gov ↗
Access the Texas House broadcast schedule via API. Retrieve committee hearing times, live stream URLs, event status, locations, and HLS stream endpoints.
What is the Texas API?
The Texas House of Representatives Broadcast API provides two endpoints that expose the full schedule of legislative events published on house.texas.gov/videos, returning up to dozens of event objects per call. The get_schedule endpoint supports date filtering and returns event-level fields including HLS stream URLs, event IDs, status, and nested location data — making it the more detailed of the two options for building viewers or monitoring tools.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/19889b09-2ffb-41f2-8eab-8e286ae96741/get_broadcast_schedule' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns all currently scheduled, live, and completed broadcast events from the Texas House of Representatives video page. Each event includes title, date, time, computed UTC start time, status, location, channel, type, and video page URL. Results are returned as a single unpaginated list of all events the site currently publishes.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer count of events returned",
"events": "array of broadcast event objects"
},
"sample": {
"data": {
"total": 17,
"events": [
{
"date": "8/17/26",
"time": "9:00AM",
"type": "committee",
"title": "Higher Education",
"format": "scheduled",
"status": "pending",
"channel": "CH 289",
"captions": true,
"category": "committee",
"duration": null,
"event_id": 22751,
"location": "E2.036",
"thumbnail": null,
"program_id": 4,
"description": null,
"series_title": "Higher Education",
"start_time_utc": "2026-08-17T15:00:00Z",
"video_page_url": "https://www.house.texas.gov/videos/22751"
}
]
},
"status": "success"
}
}About the Texas API
What the API Returns
Both endpoints pull from the Texas House of Representatives video schedule and return an array of broadcast event objects alongside a total count. Each event includes a title, date, time, start_time_utc (computed UTC timestamp), status (scheduled, live, or completed), type, and a video_page_url linking to the official event page.
Endpoint Differences
get_broadcast_schedule returns all events without filtering and includes a flat location field alongside channel. It is suitable for full-schedule pulls when you need a snapshot of everything currently listed. get_schedule adds a date query parameter (ISO format YYYY-MM-DD) to narrow results to a specific day, and its event objects include a nested location object with separate room and channel fields, an event_id string, original_start_date, an is_ea flag, and — when a stream is active — the m3u8 HLS stream URL for direct playback integration.
Coverage and Scope
The data reflects what is published on the Texas House video schedule page, which covers committee hearings and other official House proceedings. Status values distinguish between upcoming, in-progress, and past events. The start_time_utc field normalizes scheduling data for timezone-aware applications without requiring manual conversion from Central Time.
The Texas API is a managed, monitored endpoint for house.texas.gov — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when house.texas.gov changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official house.texas.gov API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display a live dashboard of Texas House committee hearings using
statusandstart_time_utcfields - Embed or link HLS streams from the
m3u8field returned byget_schedulefor active events - Filter today's legislative schedule by passing the current date to
get_schedule'sdateparameter - Send calendar notifications for upcoming hearings by monitoring
statuschanges from scheduled to live - Index completed hearings by
event_idandvideo_page_urlfor a legislative archive or search tool - Map hearing locations using the nested
roomandchannelfields fromget_scheduleevent objects - Track how often specific committee types appear in the schedule using the
typefield across date ranges
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does house.texas.gov have an official developer API?+
What does the `get_schedule` endpoint return that `get_broadcast_schedule` does not?+
get_schedule returns a nested location object with separate room and channel fields, a string event_id, an original_start_date, an is_ea flag, and the m3u8 HLS stream URL when a live stream is available. It also accepts a date parameter to filter results to a single day. get_broadcast_schedule returns a flat location field and covers all events without date filtering.Is historical broadcast data available through these endpoints?+
Are video recordings or VOD URLs returned for completed events?+
m3u8 HLS stream URL is returned by get_schedule when a stream is active, but on-demand video recordings for completed events are not currently included in the response fields. The video_page_url field links to the official event page where recordings may be available. You can fork this API on Parse and revise it to extract VOD URLs from those individual event pages.