> For the complete documentation index, see [llms.txt](https://developers.laws.africa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.laws.africa/get-started/authentication.md).

# Authentication and API keys

Authenticate Laws.Africa API requests with an API token.

Calls to the Laws.Africa APIs must be authenticated with an API token.

1. Sign up for a Laws.Africa platform account at <https://platform.laws.africa/>.
2. Create or copy your API token from <https://platform.laws.africa/api-keys/>.
3. Include the token in the `Authorization` header for API requests.

```http
Authorization: Bearer <YOUR_AUTH_TOKEN>
```

For example:

```bash
curl -H "Authorization: Bearer <YOUR_AUTH_TOKEN>" \
  https://api.laws.africa/ai/v1/knowledge-bases
```

{% hint style="info" %}
Keep your API token private. Do not commit it to source control or expose it in browser-side code.
{% endhint %}

Your API token is tied to your platform account. Your active plan and services control which Knowledge Bases, countries, localities and Content API endpoints the token can access. See [manage your plan and subscription](/get-started/manage-your-plan.md) for plan, country and usage management.

If you are logged into your platform account, you can also browse some API endpoints directly in your web browser.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.laws.africa/get-started/authentication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.