Texas State Salaries Scraper
Pricing
from $19.00 / 1,000 results
Texas State Salaries Scraper
Scrapes Texas state employee salary records from the Texas Tribune public pay database. Filter by employee name, agency, or keyword, and export each record as a flat row.
Pricing
from $19.00 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
14 days ago
Last modified
Share
Texas State Salaries Scraper
Scrape Texas state employee salaries from the Texas Tribune public pay database, up to a million records per run. Each record includes name, agency, title, and compensation. No login or API key. Export to CSV, JSON, Excel, or XML.
The Texas Tribune publishes salary data for every Texas state employee, but browsing it page by page is slow and manual. This Actor reads the public pay database directly, filtered by employee name, agency, or keyword, and returns each match in one fixed schema. You get clean, structured rows ready for analysis, journalism, or public records research.
| Who uses it | What they scrape Texas Tribune Government Salaries for |
|---|---|
| Journalists | Investigating compensation patterns across Texas state agencies |
| Government watchdogs | Monitoring public payroll for transparency and accountability |
| Researchers | Analyzing salary distributions by agency, title, or tenure |
| Job seekers | Comparing pay ranges for similar roles in Texas state government |
What it does
This Actor collects Texas state employee salary records by keyword, agency, or employee name, and returns each one as a flat row.
- ๐ Keyword search: Find records by employee name, job title, or any text in the database.
- ๐๏ธ Agency filter: Limit results to a specific Texas state agency, like the Department of Public Safety.
- ๐ Flat row output: Every record comes back as a single row with consistent fields for easy export.
- โ๏ธ Max records control: Set a hard cap from 1 to 1,000,000 records per run to manage dataset size.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Texas Tribune Government Salaries data
๐ฐ Investigate agency payrolls.
A reporter enters an agency name like 'Texas Department of Criminal Justice' and exports all salaries to find outliers or trends.
๐ Compare compensation across roles.
A researcher searches for a job title like 'engineer' across all agencies to build a salary benchmark dataset.
๐ Track individual employees.
A watchdog enters a specific employee name to pull their full salary history from the public database.
๐ Build a public pay dashboard.
A civic hacker runs the Actor weekly with no filters and feeds the CSV into a live visualization of Texas state salaries.
Why choose this scraper
| What you get | |
|---|---|
| No API key | Reads the public Texas Tribune salary database directly, no registration or OAuth. |
| Structured output | Every record is a flat row with name, agency, title, and compensation fields. |
| Flexible filtering | Search by employee name, agency, or any keyword, alone or combined. |
| Scalable | Collect up to a million records per run for large-scale analysis. |
How it compares
No other Store actor targets Texas Tribune Government Salaries the same way, so the honest comparison is with the alternatives teams actually weigh.
| Texas State Salaries Scraper | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When Texas Tribune Government Salaries changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |
Configure the run
Drive the Actor with a keyword, an agency name, or both, and set a maximum record count. Filters run as each record is read, so only matches reach your dataset. The Input tab lists every parameter.
A first run with the defaults:
A larger pull:
Pricing
Pay-per-result: $0.021 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $2.10 |
| 1,000 results | $21.00 |
| 10,000 results | $210.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Texas State Salaries Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to Texas Tribune Government Salaries through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check your keyword or agency spelling. Try a shorter or more common term, and make sure 'Maximum records' is set to at least 1. If the database has no match for your query, the run will return an empty dataset.
Why did the run stop before reaching my max records?
The Actor stops when it has read all matching records from the database. If your filters are narrow, there may be fewer matches than your max. Broaden your keyword or remove the agency filter to get more results.
Why are some fields empty in the output?
The Texas Tribune database may not have a value for every field on every record. For example, some employees may not have a listed title or agency. Empty fields are normal and reflect missing data in the source.
Can I get historical salary data?
The Actor returns the current snapshot from the Texas Tribune database. It does not provide historical records or changes over time. For historical analysis, you would need to run the Actor periodically and store the results.
FAQ
| Question | Answer |
|---|---|
| What data does this Actor return? | Each record includes the employee's name, agency, job title, and compensation details as published by the Texas Tribune. The exact fields are shown in the sample output. |
| Do I need an API key or login? | No. The Actor reads the public Texas Tribune salary database directly, so no registration or authentication is required. |
| Can I filter by agency? | Yes. Use the 'Agency' input to limit results to a specific Texas state agency, such as 'Texas Department of Transportation'. |
| Can I search by employee name? | Yes. The 'Employee or agency name' input accepts a keyword, so you can enter a full name or part of a name to find matching records. |
| How many records can I collect? | You can set the 'Maximum records' input from 1 to 1,000,000 per run. The default is 10, which is useful for testing. |
| What export formats are supported? | The Actor outputs data in CSV, JSON, Excel, and XML formats, so you can use it in spreadsheets, databases, or custom scripts. |
| Is this data up to date? | The Actor reads the live Texas Tribune database at the time of the run, so you get the latest published salary information. |
| Can I combine filters? | Yes. You can provide both a keyword and an agency name to narrow results, and the Actor applies both filters as it reads records. |
| What if I get no results? | Check your spelling and try a broader keyword. Some agencies may use abbreviations, so 'DPS' might work better than 'Department of Public Safety'. |
| Is this Actor affiliated with the Texas Tribune? | No. This Actor is an independent tool that accesses the public database. It is not endorsed by or affiliated with The Texas Tribune. |
Related actors
Browse the full ParseForge collection for more scrapers.
๐ Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
โ ๏ธ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by The Texas Tribune. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
