# Welcome to Evia Sign API Version2

Welcome to the Evia Sign API Version 2 Documentation. This API provides a secure, scalable, and developer-friendly way to integrate advanced digital signature capabilities directly into your applications. 

Whether you're building a simple signing workflow or a complex, multi-party signature process, Version 2 is designed to meet your needs with enhanced performance and robust security.

## What’s New in Evia Sign API Version 2?

Evia Sign API Version 2 is a significant upgrade over Version 1, bringing a range of improvements designed to enhance both security and usability:

### **Optimized Signing Workflow:**

* In Version 1, sending signature requests to multiple recipients in a single JSON collection often caused workflow disruptions due to timeouts.
* Version 2 introduces an optimized flow, where each signature request is processed independently, ensuring seamless, reliable multi-party signing.

### **Enhanced Security with OAuth 2.0:**

* While OAuth 2.0 was part of Version 1, the implementation has been significantly refined in Version 2.
* This enhanced implementation ensures better compliance with industry security standards, providing robust protection for your digital signatures.

### **Developer-Friendly Design:**

* A more intuitive API structure with well-defined endpoints, designed to simplify integration.
* Comprehensive, clear documentation with step-by-step guidance for various use cases.
* Practical code examples and ready-to-use templates for faster implementation

## **Why Choose Evia Sign API Version 2?**

* **Reliability:** Avoid workflow disruptions with optimized request handling, especially in high-volume signing scenarios.
* **Security:** Enjoy robust protection with OAuth 2.0, implemented using best practices for secure API authentication.
* **Scalability:** Effortlessly scale your digital signing operations, from simple one-time signatures to complex multi-party agreements.
* **Flexibility:** Support for dynamic signatory management, automated stamping, and precise document positioning.

## **Who Should Use This API?**

* **Developers:** Looking to integrate secure, flexible digital signatures into their applications.
* **Enterprises:** Needing scalable, compliant, and secure digital signing solutions for internal and external workflows.
* **Service Providers:** Offering digital signature capabilities as part of their product portfolio.

## Let’s Get Started

To make the most of Evia Sign API Version 2, follow these sections to understand its capabilities and implementation:

* **Authentication:** Learn how to securely access the API using OAuth 2.0.
* **Core API Workflows:** Discover how to create, send, and manage signature requests.
* **Error Handling:** Understand how to identify and resolve common issues.
* **Webhook Management:** Set up and manage real-time notifications for key events.
* **Code Examples:** Explore ready-made code samples for quick integration.

For any questions or support, please contact our team at <support@enadoc.com>.