TX Government Contract Awards & Winners, ESBD (tx-esbd-awards)

Who actually won the contract. This actor returns the award record behind a Texas state solicitation - the winning vendors, the amounts, their HUB status, and their VPTS vendor performance grade where a match exists.

It answers the question the opportunity feed can't: not what is being bought, but who got it, for how much, and how they performed.

Low cost

From $0.0175 per award record - you are charged per award record delivered, never for the query itself. Runs are capped at $5.

Most award records carry several winner lines; each contractor is billed as one record, so you pay for the winners you receive rather than for the solicitations scanned.

What you get

{
  "platform": "tx-esbd",
  "bidNumber": "802-27-75102-BR",
  "title": "17ft Center Console Mud Boat Packages",
  "agency": "Parks & Wildlife Department - 802",
  "nigpCodes": [{ "code": "12021", "description": "Boats, 21 Feet And Under" }],
  "contractor": {
    "name": "GULF COAST MARINE LLC",
    "value": 29266.0,
    "hubStatus": "HUB",
    "awardDate": "8/27/2026",
    "vpts": { "vendorId": "17001234567", "grade": "A" }
  }
}

Fields: platform, bidNumber, title, agency, nigpCodes (structured), contractor.name, contractor.value, contractor.hubStatus, contractor.awardDate, contractor.vpts.vendorId, contractor.vpts.grade.

Filters

Filter	What it does
nigpCodes	Award records in one or more NIGP codes.
agencies	Restrict to one or more agencies.
publishedAfter / publishedBefore	Date window (YYYY-MM-DD) - for chunking the corpus.
includeVpts	Attach the VPTS performance grade (default on).
refreshVpts	Re-pull the VPTS index instead of using the cached one.
pages	Scan depth from the newest record (24 records per page). Default 20.
maxResults	Cap the number of output records.

Example inputs

Who won in a commodity code - nigpCodes matches the structured code; widen pages to reach further back:

{ "nigpCodes": ["96145"], "pages": 250 }

Awards handed out by one agency:

{ "agencies": ["529"], "pages": 100 }

Awards inside one date window - pages sets the scan depth from the newest record:

{ "pages": 50, "publishedAfter": "01/01/2026", "publishedBefore": "12/31/2026", "maxResults": 50 }

Skip the performance lookup for a lighter, faster scan:

{ "pages": 20, "includeVpts": false, "maxResults": 50 }

Read the VPTS grade correctly

contractor.vpts is attached by matching the winner's name against the VPTS performance register. The ESBD award record carries no vendor ID, so this can only ever be a name match - measured across three recent runs, 26.6% of award winners (83 of 312) find a confident VPTS record, and the rest come back as "vpts": null. A null is "no confident match", never a guessed grade.

For exact, ID-linked vendor performance, use the CMBL actor instead - there the join is on the vendor's ID, so it is exact rather than probabilistic.

Why this is hard

Two separate sources have to be reconciled: the solicitation record (which knows what was bought and by whom, by name only) and the VPTS performance register (which knows how vendors performed, keyed by a vendor ID the award record doesn't carry). Bridging them with a name match is the only option the data allows - so the honest engineering move is to report when a match was found rather than to silently attach the nearest name.

The award detail also lives behind a second API call per solicitation - which is why the scan depth and per-run cost behave differently here than in the plain search actor.

Example output

{"nigpCodes": ["94828"]} - one award record: the solicitation, its winning contractor, and the VPTS line attached where a match exists:

{
  "platform": "tx-esbd",
  "bidNumber": "HHS0017561",
  "title": "On-site Total Intravenous Anesthesia at  Austin State Supported Living Center (AuSSLC)",
  "agency": "Health & Human Services Commission - 529",
  "agencyNumber": "529",
  "status": "Awarded",
  "nigpCodes": [
    {
      "code": "94828",
      "description": "Dental Services"
    }
  ],
  "publishedDate": "6/22/2026",
  "closeDate": "7/8/2026 10:30 AM",
  "url": "https://www.txsmartbuy.gov/esbd/HHS0017561",
  "internalId": "530056",
  "contractor": {
    "name": "Deepsedation",
    "address": "1401 Lavaca st #724",
    "value": 40000,
    "hubStatus": "2",
    "hubStatusText": "NOT CERTIFIED",
    "awardDate": "9/17/2026",
    "awardStatus": "Full Award",
    "vpts": {
      "vendorId": "18520751746",
      "vendorName": "DEEPSEDATION P C",
      "grade": "A",
      "reportCount": "2",
      "datePublished": "11/20/2025"
    }
  }
}

A winner with no confident VPTS match comes back as "vpts": null - never a guessed grade.

The rest of the Texas family

Your goal	Actor
Find bids by keyword, NIGP, agency, status	tx-esbd-search
Check one specific bid by its number	tx-esbd-get
Monitor new & changed solicitations on a schedule	tx-esbd-changes
Who won state contracts, at what amounts	tx-esbd-awards - you are here
Find / vet a vendor - HUB, SDV, small business, NIGP capability	tx-cmbl-vendors
Find disabled-veteran (DV) HUB vendors	tx-hub-certified
Statewide contracts - who's on each SPD/TxSmartBuy contract	tx-smartbuy-contracts
Pull the raw full corpus (query + monitor) - power users	sled-tx-procurement

Typical questions

• "Who won contracts in NIGP 12021 this year, and for how much?"
• "Which agencies award to HUB vendors in my category?"
• "What is the average award size in my commodity code?"
• "Is my competitor winning - and what is their VPTS performance grade?"

Notes

• Data source: Texas Comptroller - ESBD awards + TxSmartBuy Vendor Performance Tracking System (VPTS). Public state records.
• No login, no anti-bot - uses the official public JSON API.

License

MIT - see ./LICENSE.

Disclaimer

This product is an independent data service and is not affiliated with, endorsed by, or sponsored by the State of Texas or any government agency. All award data is public government information.