HigherGov
DATA · DATA & ANALYTICS
Federal contract and grant awards, opportunities, agencies, and awardees on their own key.
Connect HigherGov with Fabriq Developer
Your user pastes their HigherGov credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting HigherGov in practice
HigherGov meters records rather than requests: every subscription includes API access and 10,000 records a month, so one broad search that returns a thousand rows spends a tenth of the monthly allowance in a single call. The API key travels as an api_key query parameter, only an account administrator can create one, and the download_url a Document call returns expires after 60 minutes.
Scopes that draw scrutiny
api_key query parameterHigherGov’s documented calls put the key in the URL rather than a header, so it lands in access logs, proxies and browser history.Account administratorOnly an account administrator can generate API keys, and the full key is shown once on the API management screen, so an ordinary user cannot self-serve a credential.
Rate limits
- All HigherGov subscriptions include API access and 10,000 records per month; more requires contacting HigherGov with a use case for pricing.
- Results are paged with page_number and page_size parameters.
- Document download URLs expire 60 minutes after the Document endpoint returns them.
Who has to approve
API keys can only be generated by an account administrator, from the API management screen, and the full key is displayed there exactly once. A user without administrator rights cannot mint a credential at all, so connecting is an admin action rather than a personal one.
Worth knowing
- Because the budget is records rather than calls, an unfiltered query is expensive in a way that request-count throttling would never reveal.
- If a download_url is not used inside its 60 minutes, the Opportunity and Document calls have to be repeated — which spends records again to fetch the same file.
- search_id replays a saved HigherGov UI search as an API call but does not accept every search field, so the UI search and its API twin can legitimately return different sets.
- Freshness differs per endpoint: Opportunity updates about every 20 minutes while Federal Contract, Federal Grant and Awardee are daily, so an hourly poll of contracts spends records for nothing.
Checked against HigherGov API (2026-09-29), OAS documentation (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put HigherGov behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.