> 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. ### About Integration Integration is the central workspace for applications that access Evia Sign and for webhook endpoints that receive real-time signing events. The redesigned page separates application management from webhook delivery, while keeping linked information easy to find.

Area	Use it to
API Apps	Register and manage client applications, OAuth credentials, API keys, scopes, linked webhooks, and integration activity.
Webhooks	Create and manage tenant callback endpoints, subscribed events, security settings, connection tests, and delivery status.

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** 2. **Access API Management**

1. **Register a New Application** Click the **New App** button within the Integrations section. Fill in the required fields:


Field	Purpose
App name	A unique and recognizable name for the integration.
Redirect URI (Callback URL)	The exact callback address where Evia Sign returns the OAuth authorization code, for example https://example.com/callback.
Scopes	The API permissions the app is allowed to request.
Description	(Optional) A short description that clearly identifies your app’s purpose.
Active app	Controls whether the app can access Evia Sign.

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

1. **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.

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. {% hint style="warning" %} SECURITY | Store the client secret immediately in a protected secret manager. Treat it like a password and do not expose it in browser code, source control, or application logs. | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | {% endhint %} | ### Find, view, update, or delete an app * Use Search apps and press Enter to find apps by their details or status. * Select an app row to view its details. The list shows the app name, client ID, API-key and webhook counts, scopes, and active or inactive status. * Select the client ID badge to copy it. * Select Edit App to change the app name, redirect URL, description, scopes, or status, then select Update. * Select Delete App and confirm to permanently remove an app.