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

# Login

Questions relating to logging into the API and authenticating/authorizing requests.

<details>

<summary>I'm getting 'One or more of your API Credentials are invalid' when trying to login</summary>

There are two likely scenarios where you can get an invalid credentials error.

**You are not the Owner of your app:**

While the User Management feature of the Dashboard allows multiple users to login and view the dashboard, only an App's "Owner" username and password will allow you to generate a token.\
You can view who your App's owner is on the [team view](https://channel.violet.io/settings/team)

**You are using the wrong App Secret for the environment you are trying to login:**

While your username and password will be the same across environments (test and live) as will your `X-Violet-App-Id`, this is **not** true for your `X-Violet-App-Secret`.\
The `X-Violet-App-Secret` you retrieve from the Channel dashboard is *different* depending on the live/test mode toggle. You must use the correct app secret that corresponds to the environment you are trying to login to: `test` for `sandbox-api.violet.io` and `live` for `api.violet.io`.

</details>


---

# 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.violet.io/faqs/login.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.