DAPS Open Data API
Public query engine for GCGS commercial data. Exposes compiled OCDS releases, organisations, procurement nodes, and enriched commercial concepts as a filterable OData service for departments, suppliers, and transparency consumers.
Service information
- Environment
- PROD
- API Version
- v1
- Deployed
- 2026-07-23
Platform capabilities
The Open Data API exposes the platform's published procurement data as a queryable OData service, alongside the enrichment and validation endpoints that consuming services build on.
OData Query Engine Core
Every entity set supports $filter, $select, $orderby, $expand, $count, and $top up to 10,000 records, so consumers can shape responses without bulk downloads.
Compiled OCDS Releases Core
Full contracting records conforming to the Open Contracting Data Standard, compiled from every stage of the procurement lifecycle.
Organisation Register Data
Buyer and supplier organisation records with identifiers, addresses, and classification, resolved across the platform's source systems.
Commercial Concepts Insights
Derived views over the raw data — commercial tools, buyer planning groups, and milestone summaries — for questions the base OCDS model does not answer directly.
Payment Validation Processing
Validation endpoints that check payment payloads against the platform's schema before they enter the processing pipeline.
API Key Authentication Security
Data endpoints are protected by an X-API-Key header. Keys are issued and revoked through the DAPS Operational API.
Service endpoints
| Endpoint | URL | Description |
|---|---|---|
| API Reference |
/swagger
|
Interactive Swagger UI — browse and test all endpoints |
| OData service |
/odata
|
OData service document listing the available entity sets |
| OData metadata |
/odata/$metadata
|
EDM schema describing every entity, property, and type |
| Compiled releases |
/odata/compiledrelease
|
Compiled OCDS contracting records (API key required) |
| Organisations |
/odata/organisation
|
Buyer and supplier organisation records (API key required) |
| Health check |
/health/live
|
Liveness probe used by ECS and the load balancer |
Data endpoints require an X-API-Key header. Keys are issued by the DAPS Operational API. This landing page, the health checks, the Swagger UI and the OData service document and metadata are publicly accessible.
Support and contact
This API is maintained by the DAPS Platform team within Cabinet Office Digital. Use the channels below to get help, report issues, or request access.
General support
For access requests, API keys, or general queries about the Open Data API.
-
daps-support@cabinetoffice.gov.uk
Placeholder - Response
- 2 working days
- Hours
- Mon–Fri, 9am–5pm
Technical issues & bugs
Report query errors, unexpected results, or service degradation via the platform's issue tracker.
- Issue tracker
-
GitHub Issues (internal)
Placeholder - Slack
-
#daps-platform-support
Placeholder - P1 incidents
-
daps-incidents@cabinetoffice.gov.uk
Placeholder
Documentation & team
Platform architecture, OCDS data model reference, and API changelog.
- Confluence
-
DAPS Platform Wiki
Placeholder - OCDS standard
- Open Contracting Data Standard
- Team
- Cabinet Office Digital — DAPS