Authorization & Authentication

Evia Sign API uses OAuth 2.0 (Authorization Code Flow) to provide secure access, ensuring that only authorized users and applications can interact with the API. This method allows applications to obtain an access token that must be included in all API requests for authentication.

To securely interact with the Evia Sign API, you’ll need to authenticate your application using OAuth 2.0 Authorization Code Flow.

What is a Base URL?

The Base URL is the root address that serves as the entry point for all Evia Sign API requests. You will append specific endpoints to this base to interact with different API features (e.g., sending documents, managing signatories, tracking signatures).

Base URL: https://evia.enadocapp.com/_apis/sign

Authentication Method: OAuth 2.0 (Authorization Code Flow)

Evia Sign uses OAuth 2.0, specifically the Authorization Code Flow, which is one of the most secure methods for authorizing access to an API.

Here’s a quick breakdown of how it works:

1. App Registration

Before initiating the authentication flow, the third-party application must be registered in Evia Sign. Upon successful registration, you will receive the following:

• Client ID – A unique identifier for the application.

• Client Secret – A confidential key used for secure token exchange.

These credentials uniquely identify and authorize your app.

1. Request Authorization Code

Use the Evia Sign authorization URL, including the required parameters, to request an authorization code.

1. Authorization Code Issued

If the request is valid, Evia Sign returns an authorization code.

1. Token Exchange

Use the authorization code, along with your Client ID and Client Secret, to call Evia Sign’s token endpoint and exchange it for an access token.

1. Authenticated Requests

Once the access token is received, include it in the Authorization header to make authenticated requests to the Evia Sign API.