# TxDOT Bid Tabulations - Texas Highway Bidders & Unit Prices (`pink_comic/texas-dot-highway-bid-tabulations`) Actor

Search 1M+ TxDOT bid tabulation line items from state and local highway lettings since 2024: bidder, rank, low-bid flag, bid total, unit price, quantity, item code, engineer's estimate, project, county, district and let date.

- **URL**: https://apify.com/pink_comic/texas-dot-highway-bid-tabulations.md
- **Developed by:** [Ava Torres](https://apify.com/pink_comic) (community)
- **Categories:** Lead generation, Business, Agents
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.60 / 1,000 bid line items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## TxDOT Bid Tabulations - Texas Highway Bidders & Unit Prices

Search the **Texas Department of Transportation Bid Tabulations** file on data.texas.gov (more than 1,000,000 bid line items from about 7,500 state and local highway lettings since September 2024, updated after each letting, 17k downloads).

Each result is one bid line item for one bidder:

- **bidder name**, bid rank, low-bidder flag and **bid total**
- project ID, name, CSJ, type and classification, highway and limits
- county, TxDOT district and **let date**
- sealed engineer's estimate, DBE goal and working days
- item code, item and specification description, **quantity, unit and unit price**, engineer's estimate unit price

Results are latest letting first. By default only the apparent low bidder's lines are returned; turn **Low Bidder Only** off to compare every bidder. No API key, no CAPTCHA. Pricing: **$0.002 per line item + $0.0001 start**.

```json
{ "itemText": ["PAVEMENT MARKINGS"], "districts": ["Austin"], "letAfter": "2026-01-01", "maxResults": 500 }
```

```json
{ "projectIds": ["A00223099"], "itemCodes": ["500-"] }
```

### Use cases

Unit price history for estimators, competitor bid analysis, subcontractor and supplier leads (who won which job), DBE teaming, award tracking for material suppliers and equipment rental.

### Limits

TxDOT-administered lettings only, from late 2024 onward. Every bidder's every line is a separate row, so a full project tab can be thousands of rows; use filters and maxResults. TxDOT's own engineer's estimate is listed as bidder "Txdot Engineer's Estimate" with rank EE. Bidder contact details are not in this file.

### Related

- [Texas Business Leads](https://apify.com/pink_comic/texas-business-leads)
- [SAM.gov Contract Opportunities](https://apify.com/pink_comic/sam-gov-contract-opportunities)
- [Building Permits Construction Leads](https://apify.com/pink_comic/building-permits-construction-leads)

# Actor input Schema

## `query` (type: `string`):

Quick bidder (contractor) name search, contains match. Leave blank for the latest letting.

## `names` (type: `array`):

Contractor names, contains match, case-insensitive.

## `letAfter` (type: `string`):

Optional YYYY-MM-DD letting date.

## `counties` (type: `array`):

e.g. 'Harris', 'Travis', 'Bexar', 'Dallas'.

## `districts` (type: `array`):

e.g. 'Houston', 'Austin', 'Dallas', 'San Antonio', 'Fort Worth'.

## `projectTypes` (type: `array`):

'Construction' or 'Maintenance'.

## `itemCodes` (type: `array`):

Item code or prefix, e.g. '500-' (mobilization), '6185' (barricades), '432-'.

## `itemText` (type: `array`):

Contains match on item or specification description, e.g. 'PAVEMENT MARKINGS', 'RIPRAP', 'CONDUIT', 'GUARD FENCE'.

## `workText` (type: `array`):

Contains match on project name or short description, e.g. 'BRIDGE', 'SEAL COAT', 'WIDEN'.

## `activeOnly` (type: `boolean`):

Return only the apparent low bidder's line items (ignored for project ID and CSJ lookups, which return every bidder).

## `projectIds` (type: `array`):

Exact TxDOT project IDs, e.g. 'A00223099'.

## `csjNumbers` (type: `array`):

Exact control-section-job numbers, e.g. '0117-03-024'.

## `maxResults` (type: `integer`):

Maximum total paid dataset items, split across search terms. The default returns 10 bid line items (about $0.0201 including the start event).

## Actor input object example

```json
{
  "query": "",
  "names": [],
  "letAfter": "",
  "counties": [],
  "districts": [],
  "projectTypes": [],
  "itemCodes": [],
  "itemText": [],
  "workText": [],
  "activeOnly": true,
  "projectIds": [],
  "csjNumbers": [],
  "maxResults": 10
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset items.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "query": "",
    "names": [],
    "letAfter": "",
    "counties": [],
    "districts": [],
    "projectTypes": [],
    "itemCodes": [],
    "itemText": [],
    "workText": [],
    "activeOnly": true,
    "projectIds": [],
    "csjNumbers": [],
    "maxResults": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("pink_comic/texas-dot-highway-bid-tabulations").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "query": "",
    "names": [],
    "letAfter": "",
    "counties": [],
    "districts": [],
    "projectTypes": [],
    "itemCodes": [],
    "itemText": [],
    "workText": [],
    "activeOnly": True,
    "projectIds": [],
    "csjNumbers": [],
    "maxResults": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("pink_comic/texas-dot-highway-bid-tabulations").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "",
  "names": [],
  "letAfter": "",
  "counties": [],
  "districts": [],
  "projectTypes": [],
  "itemCodes": [],
  "itemText": [],
  "workText": [],
  "activeOnly": true,
  "projectIds": [],
  "csjNumbers": [],
  "maxResults": 10
}' |
apify call pink_comic/texas-dot-highway-bid-tabulations --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pink_comic/texas-dot-highway-bid-tabulations"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Jx6EKWaXRMzumWtzQ/builds/QIBP3W3Vjj6TdU1Pd/openapi.json