Does eSignGlobal support API integration?
Yes, eSignGlobal provides standard OpenAPI capabilities, enabling seamless integration with customer systems.
Can the signing page be embedded or integrated into third-party mobile applications?
eSignGlobal supports mobile signing page integration. Developers can:
- Use OpenAPI to create and start envelope.
- Retrieve the signing page link via OpenAPI.
- Embed this link into a third-party app (e.g., a mobile app), allowing signers to access the signing page directly within the customer’s application.
Note: Currently, mobile signing pages do not support iframe embedding.
Can the initiation page be embedded or integrated into third-party applications?
Yes, eSignGlobal supports initiation page integration. Developers can:
- Create a signing process via OpenAPI.
- Call the "Create Envelope Sender View" API to generate a link for the initiation page.
- Embed this link into a third-party application, enabling initiators to access the page directly.
Current integration methods for initiation pages:- PC iframe embedding
- Webview integration
Limitations:- Mobile initiation pages do not support iframe embedding or direct link-based integration.
eSignGlobal’s Signature Generation & Verification Mechanism
eSignGlobal currently supports Electronic Signatures and will soon support Digital Signatures (compliant with regional regulations).
Electronic Signature:
- Generation: Digital certificates are synthesized onto the signed document.
- Verification: The entire document is verified as a whole; individual signatures/seals cannot be validated separately.
Digital Signature (Upcoming):
- Generation: Digital certificates are embedded into specific signature fields.
- Verification: Enables per-signature/per-seal validation, offering higher security.
Will eSignGlobal block contract initiation in countries without e-signature laws?
For countries without enacted e-signature legislation, eSignGlobal does not proactively block contract initiation.
- eSignGlobal adheres to global legal standards to ensure validity but relies on users to comply with local regulations.
- If no specific laws exist, eSignGlobal assumes mutual agreement between parties suffices for e-signing.
- Integration partners are responsible for their own policy-based or risk-based blocking, if applicable.
How to Use the Webhook Key?
Purpose of the Webhook Key:
The webhook key is used to verify the origin of webhook messages.
Usage:
- Users obtain the key through the eSignGlobal webhook management page, sign the message body with the key according to the HmacSHA256 algorithm, and then check if it is consistent with the signature in the request header. If they are consistent, it proves that it is a webhook message pushed by eSignGlobal.
- Even without using key signature, you can still receive webhook message push notifications, but you won't be able to know the source of the webhook.