Content API for deep legal integrations
Use the Laws.Africa Content API to fetch legislation, metadata and structured formats for your own databases, publishing systems, compliance tools and offline processing workflows.
What is the Content API?
The Content API is a read-only API for listing and fetching published versions of legislative works. It provides legislation content and rich metadata for teams that need direct access to full legislative data inside their own systems.
Content formats and metadata
Content formats
- Akoma Ntoso XML
- HTML
- Table of contents (JSON)
Legislative metadata
- Publication details, including links to original government gazettes where available
- Lifecycle events, including publication, commencement, amendment and repeal
- Amendment information and related historical points-in-time (where available)
What you can build with it
Legal publishing systems
Render legislation in your own website or application using structured content and metadata.
Compliance infrastructure
Ingest and monitor applicable laws inside compliance products and internal review workflows.
Offline processing
Build pipelines for analytics, classification, search, review or local legal databases.
Webhooks for content updates
Webhooks notify your system when subscribed legislation content is created, updated or deleted. Use them to trigger background jobs that refresh your local copy or flag content for review.
Legislation available through the Content API
- African Regional Bodies
- Algeria
- Angola
- Benin
- Botswana
- Burkina Faso
- Burundi
- Côte d'Ivoire
- Democratic Republic of the Congo
- Gabon
- Ghana
- Kenya
- Lesotho
- Madagascar
- Malawi
- Mali
- Mauritania
- Mauritius
- Morocco
- Mozambique
- Namibia
- Nigeria
- Other
- Republic of the Congo
- Rwanda
- Senegal
- Seychelles
- Sierra Leone
- Somalia
- South Africa
- Tanzania
- Turks and Caicos Islands
- Uganda
- United Nations
- Zambia
- Zimbabwe
- eSwatini
Content API or Knowledge Bases?
Use Knowledge Bases when
- you need search, retrieval or AI grounding;
- you do not need to store full legislation collections locally;
- you want a fast integration path with lower operational burden.
Use the Content API when
- you need full text collections in your own system;
- you need XML, HTML, PDF, metadata or point-in-time versions;
- you are building publishing, compliance or offline processing infrastructure.
Plan your Content API integration
Review available plans, then use the developer docs to connect your product to structured legislation collections.
Plans and pricing Developer documentation