The eSAW One-Shot flow uses three main endpoints across two hosts:
| Step | Endpoint | Host | Authentication |
|---|---|---|---|
| 1. Create request | POST /api/v1/esawoneshot | Uanataca (modernpki.com) | Client certificate |
| 2. Upload file | POST /Api/v6/file/upload | eSignAnywhere (esignanywhere.net) | ApiToken header |
| 3. Send envelope | POST /Api/v6/envelope/send | eSignAnywhere (esignanywhere.net) | ApiToken header |
- Create — Creates the certificate request and returns
req_pkand esaw_token. Use esaw_token asrequestTokenin the envelope's Sign activity (GenericSigningPluginBit4idOneShot). - Files — Upload documents to be signed. One call per document; response provides FileId for the envelope.
- Envelope — Create and send the envelope with Documents (FileId) and Activities (Sign with requestToken).
Base URLs:
- Testing: Uanataca
https://api.sandbox.modernpki.com, eSAWhttps://demo.esignanywhere.net - Production: Uanataca
https://api.modernpki.com, eSAWhttps://saas.esignanywhere.net
Full request and response details are in the OpenAPI specification.
- eSAW One-Shot OpenAPI specification — All endpoints, request/response schemas, and examples
For quick API testing, use the eSAW One-Shot Postman collection. Set the host variable (and, if needed, separate hosts for Uanataca and eSAW) to your environment URLs and run the requests.
- Get started — Endpoint URLs and authentication
- Signing flow — Step-by-step create → upload → send
- Architecture — Uanataca and eSAW roles