Release: This article describes features and functionality planned for our October release. Some features may not be available until October 8, 2026.
Summary
This article provides an overview of the Bring Your Own Signature functionality.
Use Case
Classics Inc. uses Bring Your Own Signature Provider to route Ironclad signature requests through its preferred eSignature provider. A company-managed middleware service connects Ironclad to the provider, handling signature initiation, cancellations, reminders, status checks, and retrieval of signed documents while sending signature lifecycle updates back to Ironclad so workflows can continue automatically. This allows Classics Inc. to keep its existing signing process while maintaining visibility into contract execution in Ironclad.
Permissions
| Features | API |
| Permissions | To configure this integration, you must have Bring Your Own Signature Provider enabled for its Ironclad instance and have the Ironclad API entitlement. Your implementation team also needs engineers familiar with the Ironclad Public API and API authentication to build and secure the middleware service. |
What is Bring Your Own Signature?
Bring Your Own Signature Provider (BYOSP) lets companies route Ironclad signature requests through their own eSignature provider. A middleware service connects Ironclad to the provider, manages signature activity, and sends lifecycle updates back to Ironclad so the workflow can continue. This allows companies to keep their existing signing infrastructure while managing contract execution in Ironclad.
How Does It Work?
- A workflow reaches its Sign step.
- Ironclad calls the middleware service to initiate the signature request.
- The middleware service connects to the company’s eSignature provider.
- Ironclad uses the middleware service to manage the request, including cancellations, reminders, status checks, and retrieval of the signed document.
- The middleware service sends signer and request status updates to Ironclad through the Public API.
- When signing is complete, Ironclad retrieves the signed PDF and advances the workflow.
How Do I Configure It?
To configure this integration, your implementation team needs engineers familiar with the Ironclad Public API and API authentication to build and secure the middleware service.
- Ask Ironclad Support to enable BYOSP for the company’s instance.
- Confirm the Ironclad API entitlement.
- Register the provider and create a client app in Ironclad.
- Build the middleware service with the required outbound endpoints and inbound status updates.
- Configure request-signature verification and API authentication.
For detailed implementation steps, see the Bring Your Own Signature Provider developer guide.
Resources
Explore articles, courses, and support options to get the most out of Ironclad.
Help Center
Academy
- No relevant resources at this time.
Support