POST /api/saetenders/releases/search
Price: 20 credits
List the OCDS releases the South African eTenders API published on one or two release days. Each release is the full compiled tender record, the same shape saetenders/tenders returns.
This is the only date surface: a release's day is the tender's publication day, so the window is a publication window, and it is capped at two days — walk a longer range day pair by day pair. There is no other filter here; narrow by category, province or department through saetenders/tenders/search instead. A weekday publishes a couple of hundred releases and a weekend day a handful.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)date_from string required — First release day, inclusive (examples: "2026-09-17"; minLength: 10; maxLength: 10)date_to string required — Last release day, inclusive, at most one day after date_from (examples: "2026-09-18"; minLength: 10; maxLength: 10)count integer required — Max number of releases to return (min: 1; max: 500)@type string (default: "SaetendersTender")ocid string requiredrelease_id string nullableid integer requiredtender_number string nullablestatus string nullablecategory string nullabletender_type string nullableprocurement_method string nullablemain_procurement_category string nullableadditional_procurement_categories array (default: [])province string nullabledelivery_location string nullablespecial_conditions string nullablebuyer object nullable@type string (default: "SaetendersOrganisation")id string nullablename string requiredprocuring_entity object nullable@type string (default: "SaetendersOrganisation")id string nullablename string requiredamount number nullablecurrency string nullablereleased_at integer nullablepublished_at integer nullableclosing_at integer nullablehas_briefing_session boolean nullableis_briefing_compulsory boolean nullablebriefing_at integer nullablebriefing_venue string nullablecontact_name string nullablecontact_email string nullablecontact_telephone string nullablecontact_fax string nullableplanning_rationale string nullablebudget_description string nullabledocuments array (default: [])@type string (default: "SaetendersReleaseDocument")id string requireddocument_type string nullabledescription string nullableurl string nullablefile_format string nullablelanguage string nullablepublished_at integer nullablemodified_at integer nullabletenderers array (default: [])@type string (default: "SaetendersOrganisation")id string nullablename string requiredparties array (default: [])@type string (default: "SaetendersParty")id string nullablename string nullablelegal_name string nullablecountry string nullableroles array (default: [])contact_name string nullablecontact_email string nullablecontact_telephone string nullablecontact_fax string nullablewebsite string nullableawards array (default: [])@type string (default: "SaetendersReleaseAward")id string requiredsupplier string nullablestatus string nullableenterprise_type string nullableamount number nullablecurrency string nullablesuppliers array (default: [])@type string (default: "SaetendersOrganisation")id string nullablename string requiredcontracts array (default: [])@type string (default: "SaetendersContract")id string requiredaward_id string nullabledescription string nullablestatus string nullableamount number nullablecurrency string nullablesigned_at integer nullablestart_at integer nullableend_at integer nullablemax_extent_at integer nullableduration_days integer nullabledocuments array (default: [])@type string (default: "SaetendersReleaseDocument")id string requireddocument_type string nullabledescription string nullableurl string nullablefile_format string nullablelanguage string nullablepublished_at integer nullablemodified_at integer nullabletags array (default: [])initiation_type string nullablelanguage string nullableurl string required422 — The window is malformed, reversed, or longer than two days 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 — The entity was not found, or a precondition failed 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.