POST /api/canadabuys/tenders
Price: 15 credits
Get one CanadaBuys record by its reference or URL — a tender notice, an award notice or a contract history entry: title and description, status, solicitation and contract numbers, publication, closing, award, amendment and expiry dates, contract duration, procurement method, selection criteria, reason for limited tendering, delivery regions, trade agreements, UNSPSC and GSIN codes, languages, the contracting and buying organizations with addresses, the contracting authority's name, email, phone and its own postal address, the supplier with its standardized name and employee count, the amendment and total contract values, the attached documents and the third-party URL of an externally sourced notice.
A row id from canadabuys/tenders/search, canadabuys/awards/search or canadabuys/contracts/search resolves here; pass notice_kind alongside a bare reference so the right register is read, or pass the row URL and it is taken from there. Which fields are filled depends on the register: a tender notice carries the closing date and documents, an award or contract history entry carries the supplier and the values.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)notice string required — Notice reference or notice URL (examples: "cb-139-55001085", "https://canadabuys.canada.ca/en/tender-opportunities/tender-notice/cb-139-55001085", "https://canadabuys.canada.ca/en/tender-opportunities/award-notice/31184-180420001cal"; minLength: 1)notice_kind string nullable — Which register the reference belongs to, when it is passed without its URL (one of: "tender", "award", "contract_history")@type string (default: "CanadabuysNotice")id string requirednotice_kind string required (one of: "tender", "award", "contract_history")description string nullablestatus string nullablesolicitation_number string nullablecontract_number string nullablenotice_type string nullablecontract_instrument_type string nullableamendment_type string nullablepublished_at integer nullableclosing_at integer nullableawarded_at integer nullableamended_at integer nullableexpires_at integer nullablecontract_duration string nullableprocurement_method string nullableselection_criteria string nullablelimited_tendering_reason string nullabledelivery_regions array (default: [])region_of_opportunity array (default: [])trade_agreements array (default: [])unspsc array (default: [])gsin array (default: [])languages array (default: [])buyer object nullable@type string (default: "CanadabuysOrganization")name string nullableaddress string nullableend_user_organizations array (default: [])@type string (default: "CanadabuysOrganization")name string nullableaddress string nullablecontact_name string nullablecontact_email string nullablecontact_phone string nullablecontact_address string nullablesupplier object nullable@type string (default: "CanadabuysOrganization")name string nullableaddress string nullablesupplier_standardized_name string nullablesupplier_operating_name string nullablesupplier_employees integer nullableamendment_value object nullable@type string (default: "CanadabuysValue")amount number nullablecurrency string nullabletotal_contract_value object nullable@type string (default: "CanadabuysValue")amount number nullablecurrency string nullabledocuments array (default: [])@type string (default: "CanadabuysDocument")url string nullableamendment_number string nullablelanguage string nullabledownloads integer nullableadded_at integer nullablecountry string (default: "CA")external_notice_url string nullableurl string required422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — No notice with this reference on CanadaBuys Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.