Find source records
Query DIBBS RFQs with source=dibbs, then fetch a stable record by ID.
DLA DIBBS request-for-quote postings with package pages, PDFs, technical-document metadata, and searchable extracted text where enrichment has run.
dibbs-rfqsUpstream: www.dibbs.bsm.dla.mil/Confirm the source role, then follow the route families that expose it. Field-level response shapes and examples stay in the API docs.
Query DIBBS RFQs with source=dibbs, then fetch a stable record by ID.
Find terms in attachments and extracted text without building a document pipeline first.
Use notice records when you need source-verbatim fields, identifiers, and publication history.
Read recent observed changes for monitoring and incremental sync workflows.
130,356
48,023 rows with RFQ PDFs; 39,494 rows with extracted text; 39,494 indexed text documents; 1,087,406 indexed text chunks; 15,541 technical-document rows
Latest lakehouse ingest: Jul 8, 2026, 1:31 PM UTC
Per record
Daily
Responses preserve source names and source record identifiers for audit and replay.
DIBBS (DLA)
Public API routes and MCP tool groups that serve this source today.
Use this value where a route accepts source filtering.
Public /v1 route families listed below.
Tool groups share the same key and monthly quota as REST.
Search and fetch normalized opportunity records.
/v1/opportunities/v1/opportunities/{recordId}Search extracted text and list source attachments.
/v1/documents/search/v1/opportunities/{recordId}/documentsRead source-verbatim notices when provenance matters.
/v1/notices/v1/notices/{recordId}Track recently observed source changes.
/v1/changesFilter and roll up structured opportunity features.
/v1/opportunities/analysis/v1/opportunities/analysis/rollupsEvery source ships with the same auth, the same envelope, and the same docs. Get an API key and you're three minutes from your first request.