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

# Authentication

Authenticate your API calls by including your access token in the Authorization header of every request you make. You can retrieve your access token under the settings tab on the dashboard.

Authorization headers should be in the following format: `Authorization: Bearer SECRET_KEY`

Any requests made without authentication will fail with the status code `401: Unauthorized`. Also, all Live API requests must be made over HTTPS. 

Access keys on the API do not expire, unless you generate a new key. You can create a new key under the settings tab on the [Terminal dashboard](https://dashboard.terminal.africa).

#### API Endpoints:

Test Endpoint: `https://sandbox.terminal.africa/v1`

Live Endpoint: `https://api.terminal.africa/v1`


---

# 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://docs.terminal.africa/tship/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.