{"slug": "introducing-the-tenders-sa-developer-api-v2-1-0-live-south-african-procurement", "title": "Introducing the Tenders-SA Developer API v2.1.0 — Live South African Procurement Data, AI Enrichment & Compliance Tools", "summary": "Tenders-SA released version 2.1.0 of its Developer API, providing structured, real-time access to South African public sector procurement data. The API aggregates and normalizes tender notices, contract awards, supplier intelligence, forensic risk checks, and CIPC data from fragmented government portals into a single REST endpoint. It includes AI enrichment features that generate summaries, key requirements, and confidence scores for each tender.", "body_md": "The Tenders-SA Developer API gives developers structured, real-time access to South African public sector tenders, contract awards, supplier intelligence, forensic risk checks, and CIPC data — all from a single REST API.\n\nSouth African government procurement is fragmented across dozens of portals — National Treasury eTenders, Eskom, Transnet, SANRAL, nine provincial systems, and hundreds of municipal platforms. Each publishes data in different formats, on different schedules, with inconsistent structure.\n\nThe **Tenders-SA Developer API v2.1.0** solves this. It aggregates, normalises, and enriches all of that data into a single, consistent REST API that developers can integrate in minutes.\n\nThis post covers what's available, how the data pipeline works, and how to make your first API call.\n\nThe API is versioned at `https://api.tenders-sa.org`\n\nand organises data across these core domains:\n\n| Domain | What you get |\n|---|---|\nTenders |\nLive notices, search, filters, amendments, OCDS identifiers |\nAwards & Contracts |\nAwarded supplier, value, contract dates, status |\nOrganisations |\nGovernment departments and issuing entities |\nSuppliers |\nContractor profiles and contract history |\nDirectors & CIPC |\nCompany registrations, director lookups, enriched profiles |\nForensic |\nNational Treasury restricted supplier checks with fuzzy matching |\nDocuments |\nTender document metadata and secure download URLs |\nIntelligence |\nMarket alerts, sector insights, curated intel items |\nProvinces & Categories |\nReference data, health scores, industry benchmarks |\nOCDS |\nOpen Contracting Data Standard party data |\n\nEvery endpoint requires a Bearer token:\n\n```\nGET /v2/tenders\nAuthorization: Bearer YOUR_TSA_API_KEY\n```\n\nGet your key at [tenders-sa.org/developers](https://www.tenders-sa.org/developers).\n\nFetch active tenders filtered by province and category:\n\n```\ncurl -G https://api.tenders-sa.org/v2/tenders \\\n  -H \"Authorization: Bearer YOUR_TSA_API_KEY\" \\\n  --data-urlencode \"province=gauteng\" \\\n  --data-urlencode \"status=active\" \\\n  --data-urlencode \"limit=10\"\n```\n\nA typical tender response includes:\n\n```\n{\n  \"id\": \"tnd_01j...\",\n  \"title\": \"Supply and Delivery of ICT Equipment\",\n  \"source_organization\": \"Department of Basic Education\",\n  \"province\": \"Gauteng\",\n  \"closing_date\": \"2025-08-15T12:00:00Z\",\n  \"estimated_value\": 4500000,\n  \"bbbee_requirements\": \"Level 1-2 preferred\",\n  \"ai_summary\": \"Procurement of laptops, tablets, and networking equipment for school connectivity programme.\",\n  \"ai_key_requirements\": \"CIPC registration, valid tax clearance, minimum 3 years supply experience\",\n  \"ai_confidence\": 0.94,\n  \"status\": \"active\"\n}\n```\n\nNotice the `ai_*`\n\nfields — these are not raw scraped data. Every tender passes through an enrichment pipeline before it reaches the API.\n\nRaw government procurement data is rarely usable as-is. Before any record is available through the API, it goes through the following stages:\n\n**1. Ingestion** — OCDS feeds are pulled from all major government sources on a continuous sync schedule.\n\n**2. Normalisation** — Fields are standardised across sources: dates into ISO 8601, values into ZAR floats, provinces into canonical slugs, categories into a consistent taxonomy.\n\n**3. AI Enrichment** — Each tender is processed by an AI pipeline that extracts:\n\n`ai_summary`\n\n— plain-language description of what's being procured`ai_key_requirements`\n\n— eligibility and submission requirements`ai_title_enriched`\n\n— corrected/expanded title where the original is vague`ai_confidence`\n\n— model confidence score (0–1)`analysis_quality_score`\n\n— overall data quality rating**4. Document Analysis** — Where tender documents are available, they're fetched, extracted, and analysed. The `document_analyzed`\n\nflag and `ai_key_points`\n\nfield indicate when document-level intelligence is present.\n\n**5. Deduplication** — Cross-source duplicates are detected and flagged via `is_duplicate`\n\nand `duplicate_of`\n\nfields, so your application doesn't surface the same opportunity twice.\n\nOne of the most requested capabilities for procurement platforms is supplier risk screening. The API exposes the National Treasury restricted suppliers register with two endpoints:\n\n**Fuzzy match** — returns ranked candidates:\n\n```\ncurl \"https://api.tenders-sa.org/v2/forensic/restricted-suppliers/match?q=Acme+Construction\" \\\n  -H \"Authorization: Bearer YOUR_TSA_API_KEY\"\n```\n\n**Point-in-time check** — returns a boolean clearance result:\n\n```\ncurl \"https://api.tenders-sa.org/v2/forensic/restricted-suppliers/check?q=Acme+Construction\" \\\n  -H \"Authorization: Bearer YOUR_TSA_API_KEY\"\n```\n\nCombined with CIPC director lookups (`/v2/cipc/directors`\n\n), this enables full entity due diligence without leaving the API.\n\nThe `/v2/cipc/enrichments`\n\nand `/v2/cipc/directors`\n\nendpoints surface Companies and Intellectual Property Commission data linked to suppliers in the procurement dataset. This is useful for:\n\nEach province has a health score endpoint that surfaces aggregated procurement health metrics:\n\n```\nGET /v2/provinces/{id}/health-scores\n```\n\nThis is useful for building regional procurement dashboards or benchmarking spend patterns across provinces.\n\nAll tender records carry an `ocid`\n\nfield conforming to the [Open Contracting Data Standard](https://standard.open-contracting.org/). The `/v2/ocds/parties`\n\nendpoint exposes structured party data for interoperability with other OCDS-compliant systems — useful if you're building on top of global procurement transparency tooling.\n\n``` js\nconst BASE = 'https://api.tenders-sa.org/v2';\nconst KEY = process.env.TSA_API_KEY;\n\nasync function fetchTenders(province = 'gauteng', limit = 20) {\n  const params = new URLSearchParams({ province, status: 'active', limit });\n  const res = await fetch(`${BASE}/tenders?${params}`, {\n    headers: { Authorization: `Bearer ${KEY}` }\n  });\n  if (!res.ok) throw new Error(`API error ${res.status}`);\n  return res.json();\n}\n\nasync function checkSupplier(name) {\n  const params = new URLSearchParams({ q: name });\n  const res = await fetch(`${BASE}/forensic/restricted-suppliers/check?${params}`, {\n    headers: { Authorization: `Bearer ${KEY}` }\n  });\n  return res.json();\n}\npython\nimport os, httpx\n\nBASE = \"https://api.tenders-sa.org/v2\"\nHEADERS = {\"Authorization\": f\"Bearer {os.environ['TSA_API_KEY']}\"}\n\ndef fetch_tenders(province=\"gauteng\", limit=20):\n    r = httpx.get(f\"{BASE}/tenders\", headers=HEADERS,\n                  params={\"province\": province, \"status\": \"active\", \"limit\": limit})\n    r.raise_for_status()\n    return r.json()\n\ndef check_supplier(name: str):\n    r = httpx.get(f\"{BASE}/forensic/restricted-suppliers/check\",\n                  headers=HEADERS, params={\"q\": name})\n    r.raise_for_status()\n    return r.json()\n```\n\nThe v2.1.0 release stabilises the core data model and enrichment pipeline. Upcoming work includes webhook support for real-time tender alerts, expanded SDK coverage, and additional AI matching endpoints for supplier-to-opportunity recommendations.\n\nIf you're building on the API or have questions, open an issue on [GitHub](https://github.com/Tenders-SA) or reach out via the [developer portal](https://www.tenders-sa.org/developers).\n\n*Built for developers who want to work with South African procurement data — without the scraping, cleaning, and normalisation overhead.*", "url": "https://wpnews.pro/news/introducing-the-tenders-sa-developer-api-v2-1-0-live-south-african-procurement", "canonical_source": "https://dev.to/freelancingsolutions/introducing-the-tenders-sa-developer-api-v210-live-south-african-procurement-data-ai-98p", "published_at": "2026-06-15 10:58:45+00:00", "updated_at": "2026-06-15 11:15:15.619452+00:00", "lang": "en", "topics": ["developer-tools", "artificial-intelligence", "natural-language-processing"], "entities": ["Tenders-SA", "National Treasury eTenders", "Eskom", "Transnet", "SANRAL", "CIPC", "Open Contracting Data Standard"], "alternates": {"html": "https://wpnews.pro/news/introducing-the-tenders-sa-developer-api-v2-1-0-live-south-african-procurement", "markdown": "https://wpnews.pro/news/introducing-the-tenders-sa-developer-api-v2-1-0-live-south-african-procurement.md", "text": "https://wpnews.pro/news/introducing-the-tenders-sa-developer-api-v2-1-0-live-south-african-procurement.txt", "jsonld": "https://wpnews.pro/news/introducing-the-tenders-sa-developer-api-v2-1-0-live-south-african-procurement.jsonld"}}