GovDash API
The GovDash API connects your systems and agents to the data your team keeps in GovDash. Read and write the opportunities you're pursuing, the contracts you've won, and the agencies, companies, and people in your Data Library. Start and monitor GovDash agents from your own code.
Stability
/v1 is our first stable API surface, available as a research preview. We aim to preserve backward compatibility with its published OpenAPI schema while shipping useful improvements quickly.
- We release a deliberately focused set of endpoints so we can support them for the long term. Tell us what you need; we expand the API as integrations need more capabilities.
- We may add endpoints, optional parameters, response fields, and enum values without a new version. Ignore unknown response fields and handle unknown enum values.
- Changes that break the documented response shape ship in a new dated version. Send the
govdash-versionheader to choose the version your integration expects. - Before removing an endpoint or field, we announce a deprecation, normally with at least 30 days to migrate. It stays functional until the announced deadline. After that, an older version may return a placeholder of the same type instead of live data.
- If we need to make a change with less than 30 days' notice, we email everyone who has created an API key. The documented API is our compatibility boundary; undocumented behavior may change.
We try to deprecate as little as possible. Our planned MCP integration will have more room to evolve; the public API is intended for integrations that need a predictable contract.
Questions, feedback, or something you need? Email [email protected].
Base URL
The base URL below uses the origin serving these docs, including local and self-hosted deployments. Resource endpoints use the /v1 prefix.
https://api.govdash.us/v1Developer settings shows the base URL for your environment. If your organization uses another GovDash deployment, open Settings → Developer in that deployment. The examples in these guides read it from a GOVDASH_API_URL environment variable, so you can paste them as is:
export GOVDASH_API_URL="https://api.govdash.us"
export GOVDASH_API_VERSION="2026-11-17"
export GOVDASH_API_KEY="gd_live_..."Production API connections require HTTPS. Local development may use HTTP.
Resources
| Resource | What it holds |
|---|---|
| Opportunities | Opportunities your team is pursuing, with their phase and custom fields. |
| Contracts | Contract awards your team tracks, with their past performance write-ups. |
| Documents | Files in your team's Data Library. |
| Agencies | Government agencies in your team's Data Library. |
| Companies | Companies in your team's Data Library, such as teaming partners and competitors. |
| People | People in your team's Data Library, such as key personnel and contacts. |
| Agents | GovDash agents your team has set up, with their goals and triggers. |
| Agent runs | Runs of those agents. Start a run, check its status, and read its results. |
| Metadata | Your team's phase and custom field definitions. |
Resource endpoints under /v1 need an API key. See Authentication. Each endpoint's page in the API reference lists its parameters, shows the request in curl, TypeScript, Python, Go, Java, C#, Ruby, and PHP, annotates the response, and lets you send the request with your own key.
Download the OpenAPI document at /openapi.json to generate a client or inspect the API schema. No API key or version header is required.
Next steps
- Make your first call in the Quickstart.
- Read Requests and responses for the conventions every endpoint shares.
- Read how rate limits and errors work before you ship.