> 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/prism/overview/create-a-violet-application.md).

# Create a Violet Application

## About Violet Applications

Violet Applications provide you with the necessary credentials and tools to invoke our APIs and build your new system. Violet applications are the entry point to any system built on Violet and manage merchants you've connected to.

You can learn more about Violet Applications here [Apps](/concepts/apps.md), but for now, follow the steps below to continue with this recipe and create your first Violet Application.

## Create an App

1. Sign up at [channel.violet.io/signup](https://channel.violet.io/signup) or login at [channel.violet.io/login](https://channel.violet.io/login)
2. You will be asked to Create an Org, select a slug you feel comfortable with for use across your team
3. Invite other member of your team (you can do this later, too)
4. Name your application (don't worry, you can change this later as many times as you'd like).
5. Save your App ID and App Secret, you will need them for API authentication.


---

# 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/prism/overview/create-a-violet-application.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.