# Texas Esbd Solicitations Scraper (`chimerical_quicklime/texas-esbd-solicitations-scraper`) Actor

Texas ESBD Government Bids & RFPs Scraper. Structured data export for lead generation, enrichment, and competitive research.

- **URL**: https://apify.com/chimerical\_quicklime/texas-esbd-solicitations-scraper.md
- **Developed by:** [Khrystyna Skotte](https://apify.com/chimerical_quicklime) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Texas ESBD Government Bids & RFPs Scraper

Scrapes the **Texas Electronic State Business Daily (ESBD)** — the official posting board for bids, RFPs, RFQs and awards from Texas state agencies, universities and Texas SmartBuy members. Newest solicitations first, with the full detail page for each.

### What you get

Per solicitation: `solicitationId`, `title`, `url`, `agencyNumber`, `status` (Posted, Addendum Posted, Closed, Awarded…), `postingDate`, `dueDate`, `dueTime`, `createdDate`, `lastUpdated`, plus from the detail page: `contactName`, `contactPhone`, `contactEmail`, `postingRequirement`, `procurementCertification`, `classCodes` (NIGP class/item codes with descriptions), `description`, and `attachments` (name, download URL, description).

```json
{
  "solicitationId": "754-TXST-2026-RFP-511-VPIT",
  "title": "Library Digital Collection Platform",
  "url": "https://www.txsmartbuy.gov/esbd/754-TXST-2026-RFP-511-VPIT",
  "agencyNumber": "754",
  "status": "Posted",
  "postingDate": "8/19/2026",
  "dueDate": "9/8/2026",
  "dueTime": "3:00 PM",
  "contactName": "Lauren Clawson",
  "contactPhone": "(512) 245-2447",
  "contactEmail": "lauren.clawson@txstate.edu",
  "classCodes": [{ "code": "20859", "description": "Library Information Management and Library Catalog Database Software, Microcomputer" }],
  "description": "The University desires to enter into a non-exclusive Contract ...",
  "attachments": [{ "name": "ESBD Posting - Library Digital Collection Platform RFP.docx", "url": "https://www.txsmartbuy.gov/core/media/media.nl?id=...", "description": "Solicitation Notification and RFP link" }]
}
```

### Input

| Field | Default | Notes |
|---|---|---|
| `status` | `open` | `open` (Posted / Addendum Posted), `closed`, or `all` |
| `agencyNumber` | `""` | Optional agency / SmartBuy member number, e.g. `601` (TxDOT) |
| `includeDetails` | `true` | Fetch each solicitation page for contacts, NIGP codes, attachments |
| `maxItems` | `10` | Newest first |

### Use cases

Bid monitoring for government contractors, procurement intelligence, buyer contact discovery (every posting lists a named purchaser with email and phone), NIGP-code market sizing, and feeding CRM or alerting pipelines.

### Pricing

Pay per event: a small start fee plus a per-solicitation fee. A default run (10 solicitations) costs about five cents.

# Actor input Schema

## `status` (type: `string`):

Only return solicitations with this status.

## `agencyNumber` (type: `string`):

Optional Texas agency / SmartBuy member number to filter by (e.g. '601' for TxDOT, '754' for Texas State University).

## `includeDetails` (type: `boolean`):

Fetch each solicitation page for contact name/email/phone, NIGP class codes, description and attachments. One extra request per record.

## `maxItems` (type: `integer`):

Maximum number of solicitations to return (newest first).

## Actor input object example

```json
{
  "status": "open",
  "agencyNumber": "",
  "includeDetails": true,
  "maxItems": 10
}
```

# Actor output Schema

## `records` (type: `string`):

Dataset of scraped records (JSON).

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("chimerical_quicklime/texas-esbd-solicitations-scraper").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("chimerical_quicklime/texas-esbd-solicitations-scraper").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 '{}' |
apify call chimerical_quicklime/texas-esbd-solicitations-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,chimerical_quicklime/texas-esbd-solicitations-scraper"
        }
    }
}

```

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/2N9eC6LFT5WfVHApR/builds/oOI8tylucctXwm1vg/openapi.json