API key.

Government contract registers as JSON. Keys issued after review.

Data price
Enterprise Data
By agreementcontract by month or quarter
  • Whole register. Every country of the site as bulk files, then daily changes: new awards, amendments, end dates
  • Contract rows. Buyer, supplier, value, dates, procedure and bids. Canada and the United States
  • Buying office. The procurement mailbox of the buying office, as published
  • Contracts ending. End dates in a chosen window, by line
  • Uncontested awards. No competition or one bid, every country of the layer
  • Entity resolution. Amendments collapsed to the final value; supplier spellings merged into one record
  • Daily cycle. Collected, normalised, de-duplicated and checked each day; every row stamped with its update date
  • Private endpoint. A dedicated endpoint and storage bucket per company, isolated keys, no rate limits
  • SLA 95%. Monthly uptime commitment in the contract, with a 5% service credit
  • Security. TLS only, keys issued after review, records naming private persons removed, every row with its source, licence and record reference
  • Contract. By month or quarter; invoice per period; named contact
Data Provenance & Security Whitepaper →

Terms of the key

  • A key belongs to the person or company it was issued to. It is not shared, resold or published.
  • Enterprise Data: scope, delivery, service levels and use are set by the contract, by month or quarter; no resale of the data.
  • No key carries a daily limit.
  • The register is compiled from public records of each country under their licences; each record names its source.
  • A key used against these terms is closed.