For developers & AI builders

API & data access

Every Canadian government opportunity we track exists as structured OCDS data. Three ways to get at it — two free, one for scale.

1 · llms.txt — for AI agents

Our content is served as clean markdown to AI crawlers, and our facts file is public. If you're building with LLMs — copilots, research agents, procurement dashboards — this is the machine-readable entry point.

Any page also renders as markdown when requested with an Accept: text/markdown header.

2 · The REST API — Enterprise

Full programmatic access to the opportunity database. OCDS-native responses, cursor pagination, webhook push on new postings and amendments. Included with the Enterprise plan; keys are scoped per integration.

MethodEndpointDescription
GET/api/v1/opportunitiesPaginated opportunity feed. Filter by trade, province, value range, closing window, buyer, procurement type.
GET/api/v1/opportunities/{id}Full OCDS release for one opportunity, including documents and amendment history.
GET/api/v1/opportunities/{id}/documentsDocument manifests (title, mime, hash, size) with fetch URLs.
GET/api/v1/sourcesThe 24 monitored procurement sources with coverage metadata.
POST/api/v1/webhooksSubscribe to new-opportunity and amendment events (HTTP webhook or email digest).

Want a key or a custom feed (S3 dump, daily CSV, direct DB replica)? [email protected] — we shape delivery to your stack.

3 · Data licensing

The underlying procurement listings are public government records. Our aggregation, normalization and amendment diffing are available for redistribution under license — newsrooms, market-research firms and economic trackers currently ask most. Same address as above.

Not a developer?

None of this is required to use PubSec.Pro — browse the opportunities free and let the proposal generator do the technical part.