Addo Sign offers two distinct APIs, depending on your integration requirements:
New API (Recommended for all new integrations)
Legacy REST API (Supported for existing integrations, but not recommended for new ones)
New Addo Sign API (Recommended)
We’ve released a new API for Addo Sign, designed for improved performance, modern authentication, and extended capabilities.
This is the preferred API for any new integration, and we strongly encourage migrating existing integrations when practical.
🔗 Access the documentation here: https://demo.addosign.net/api/
The link takes you directly to the “Obtaining an Access Token” section of the new API docs.
Highlights of the new API:
Uses a modern token-based authentication flow (see linked section).
Cleaner endpoint structure and updated request/response formats.
Designed for better longevity and compatibility with future Addo Sign features.
Ideal for green-field projects or when you plan to future-proof your integration.
Legacy REST API
The legacy Addo Sign REST API continues to be available for customers with existing integrations. However, it is not recommended for new development.
Key aspects:
Paid access is required for usage.
Built on HTTP/REST standards; allows service-to-service interaction without direct user intervention.
Full documentation can be found here: github.com/addosign/addosign
Pricing and access details: contact our Sales team.
Authentication Requirements
New API: Follow the authentication steps defined in the new API documentation link above (Obtaining an Access Token section).
Legacy API: Log in with your Addo Sign credentials and follow the token generation process as described in the legacy docs.
Developer Support
If you need assistance during your integration, we can allocate a developer resource to support you.
Please note: This is a paid service.
From Development to Production
Once you have completed development against the demo or sandbox environment, you can replicate the setup in your production environment. An integration user is used for production access.
We recommend using the new API for production deployments unless you’re locked into the legacy architecture.