OpenGov Datasets API
**Datasets** are collections of data that can be retrieved using the API.Datasets can be retrieved by using `GET` requests. The base url for datasets is `https://api.procurement.opengov.com/gateway/datasets/v1/`Note: All dates and times returned by this API are in the time zone selected by the agency.## Datasets Legacy Authentication MethodsIn addition to the OpenGov standard Authorization header, for historic purposes we support two additional ways for the Datasets APIs.### 1. HTTP Basic AuthUse your OpenGov account email as the username and your API key as the password.```bash curl -u "alice@example.com:YOUR_API_KEY" \ https://api.procurement.opengov.com/gateway/datasets/v1/solicitations ```### 2. X-api-key headerYou may also authenticate using the `x-api-key` request header:```bash curl -H "x-api-key: YOUR_API_KEY" \ https://api.procurement.opengov.com/gateway/datasets/v1/solicitations ```> **Security note:** Some third-party systems may log or store custom headers in plaintext. To obtain an API key, please follow the steps outlined in this guide [OpenGov Procurement API Reference](https://opengov.my.site.com/support/s/article/87a452ae-254c-4b62-8336-d475c2e30723) or contact OpenGov support.The API will return a 401 error if the key is invalid.
OpenGov Datasets API is one of 102 APIs that OpenGov publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Datasets. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a changelog.
This API exposes 14 operations across 14 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.0.
Requests are made against a single base URL, https://api.procurement.opengov.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 5
OpenGov Datasets API declares
5 security schemes
for authenticating requests.
It accepts HTTP basic authentication (basicAuth).
An API key is passed in the header as Authorization (apiKeyAuth).
An API key is passed in the header as x-api-key (xApiKeyHeaderAuth).
An API key is passed in the header as Authorization (APIKey).
It accepts HTTP bearer tokens (JWT) (BearerToken).
APIKey— Format: Token your-api-key-hereBearerToken— Enter Bearer Token without Bearer prefix
Paths & Operations 14
Across 14 paths, the API surfaces 14 operations — 14 GET. Each is listed below with its method, path, parameters, and response codes.
Datasets are collections of data that can be retrieved using the API. Datasets can be retrieved by using GET requests. The base url for datasets is https://api.procurement.opengov…
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Contract (41 properties), Solicitation (37 properties), VendorSubscriber (36 properties), VendorCompany (30 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from OpenGov 12
Other APIs OpenGov publishes across the network.
This is an independent, third-party profile of OpenGov Datasets API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.