> For the complete documentation index, see [llms.txt](https://typless.gitbook.io/typlessapi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://typless.gitbook.io/typlessapi/authorization.md).

# Authorization

Our API uses an API key to authorize your requests.\
Upon successfully registering on [**Typless**](https://app.typless.com), an API key is automatically generated for you.\
If you are logged in, you will see your API key: `Token YOUR-API-KEY`.

You can also obtain your **API key** by:

1. Going to the [API Keys](https://app.typless.com/settings/api-keys) page.
2. Copying the **API key** value under the API key section.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePXqOCeLb4FOuZhmYG8X%2Fuploads%2FXwpyvlMgoIW7PXZKkPwE%2FREC-20260515112641.mp4?alt=media&token=810fbc33-d3d7-4687-b49c-62abae6c7029>" %}
Getting your API key
{% endembed %}

{% hint style="warning" %}
📘 <mark style="color:red;">**Authorizing your requests**</mark>

To successfully authorize your request, you must provide the **API key** in the header of your request under the key **Authorization**, and it must be prepended with the word **Token**.
{% endhint %}

What’s Next

Successfully got your API key? Great!\
Let's start using it. Find your use case and put it to the test!


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://typless.gitbook.io/typlessapi/authorization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.