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

# Authentication

Generate API credentials to authenticate and access Medianova APIs.

API authentication in Medianova is managed through secure token generation in the [Medianova Control Panel](https://cloud.medianova.com). After creating a token, you will receive your API credentials (API Key and Secret), which authorize access to analytics and operational endpoints across the platform.

{% hint style="info" %}
Each token remains valid for 30 days and can be renewed anytime from the Medianova Control Panel.
{% endhint %}

To view or manage your tokens, log in to the Medianova Control Panel, navigate to **Profile → My Account → API Tokens**, and click **Generate Token** to create a new credential. Store the generated token securely — it will be displayed only once.

{% openapi src="/files/vF77uhhdRcGnYha56lMc" path="/api/v1/auth/login/token" method="post" %}
[Authentication.json](https://542970813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtK7oIwmhUHdEJcaH4Hx8%2Fuploads%2Fgit-blob-5b943f23ac5c6aa6b8d9100d912b985324d4df24%2FAuthentication.json?alt=media)
{% endopenapi %}


---

# 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://clients.medianova.com/api-documentation/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.