Evia Sign
  • Welcome to Evia Sign
    • What can Evia Sign do?
  • How to send signature request?
    • How to enable multiple signatories to access and sign documents at the same time?
    • How to add approvers and CC recipients to a signature request?
    • How do you add authentication to your request?
    • How do you send a private message?
  • How to sign documents?
    • Opening a document through Evia Sign inbox
    • Explore the different ways to add your signature
  • How to draft documents?
    • Components of DRAFTS in Evia Sign
  • Explore Evia Sign Inbox
  • How to create and use templates
    • Components of TEMPLATES
  • How to save your signature and initial?
  • How to add date stamp to your signature?
  • How to set up automatic reminders & expiration for signature requests
  • Users
    • How to import O365 users?
    • How to add new users?
    • How to delete users?
    • How to activate and deactivate users?
  • How do I change the current subscription plan of my account?
    • How to cancel and renew plan?
    • How do I purchase additional user licenses?
  • How to work with Enadoc Integration?
  • Terms to be familiar
  • FAQs
    • How to login into Evia Sign?
    • How do I make an account recovery?
    • How do you configure stamps?
    • How do you manually send reminders to signatories?
    • How do you view document history?
    • How do you decline a document?
    • How do you download a document?
    • What is a digitally certified document?
    • How are additional user licenses purchased?
    • How do you send reminders to signatories?
    • How to modify your session duration?
    • How do I monitor the request usage of my Evia Sign account?
  • Release Notes
  • Evia Sign API
    • V1
      • Overview
      • Authorization of the API Access
      • Requests
        • Document Upload
        • Send Requests
      • Request Types
        • Template
        • Fixed Positioning
        • Auto Stamping
    • V2
      • Welcome to Evia Sign API Version2
      • How to Migrate from API v1 to v2
        • Basic Guide with minimal changes
        • Access Token Request (v1 âžž v2)
      • Authorization & Authentication
        • How to Register Your Application
        • Requesting the Authorization Code
        • Exchange Authorization Code for Access Token
      • Upload Document for Signing
      • Creating a Signature Request
      • Add Signatory to a Signature Request
      • Add Stamps to a Signatory
      • Send Signature Request
      • Webhook Management
      • Glossary & Common Fields
  • Welcome to the New and Improved Evia Sign
  • How to Use the PDF Commenting Feature in Evia Sign
  • How to Upload Documents from SharePoint in Evia Sign
Powered by GitBook
On this page

Was this helpful?

  1. Evia Sign API
  2. V2
  3. Authorization & Authentication

How to Register Your Application

PreviousAuthorization & AuthenticationNextRequesting the Authorization Code

Last updated 25 days ago

Was this helpful?

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

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

  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.