> For the complete documentation index, see [llms.txt](https://docs.sign.enadocapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sign.enadocapp.com/evia-sign-api/v2/authorization-and-authentication/how-to-register-your-application.md).

# How to Register Your Application

Before any authentication can take place, your application must be registered within the Evia Sign platform. This registration process allows Evia Sign to recognize and securely authorize your application. Once registered, you’ll receive a **Client ID** and **Client Secret**, which are required to initiate the OAuth 2.0 Authorization Code Flow.

These credentials serve as the foundation for all secure interactions between your application and the Evia Sign API.

Follow the steps below to register your application on the Evia Sign platform:

1. **Access API Management**\
   Go to the **Settings** section, then click on **Integrations**

<figure><img src="/files/7a9UkPeigKLihbKDQmed" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/urs8fifXw31qh6QcqSNw" alt=""><figcaption></figcaption></figure>

3. **Register a New Application**

Click the **New App** button within the Integrations section.

Fill in the required fields:

* **App Name** – A unique and recognizable name for your application.
* **Redirect URI (Callback URL)** – The endpoint on your system where Evia Sign will send the authorization code.
* **Description** – A short description that clearly identifies your app’s purpose.

Once all details are provided, click **Save**.

<figure><img src="/files/rd8EUaLC21ozzSupi6o2" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/1t2l58prHy1cEW1QWuPR" alt=""><figcaption></figcaption></figure>

4. **Save and Retrieve Credentials**

   After saving, the system will generate the following credentials:

   * **Client ID** – Used to identify your application during the authorization process.
   * **Client Secret** – A confidential key used to securely authenticate your app during token exchange.

<figure><img src="/files/St8r8IHVvJK9feNU8iAL" alt=""><figcaption></figcaption></figure>

Once your application is registered and you’ve secured your **Client ID** and **Client Secret**, you’re ready to move on to the next step—**requesting the authorization code** needed to initiate the access token flow.


---

# 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://docs.sign.enadocapp.com/evia-sign-api/v2/authorization-and-authentication/how-to-register-your-application.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.