One-Shot supports several workflow types. Each workflow shares the same principle: a signature request is created, documents (or hash payloads) are associated, the user is identified (e.g. OTP or VideoID), and the single-use certificate is issued and used to sign. Signed documents (or signed P7M) are then retrieved.
The exact steps and API calls depend on the workflow. For the full list of workflow types with descriptions and when to use each, see the Workflows overview.
In most workflows you will:
- Obtain or create an RAO token (sandbox provides a default token; production requires creating tokens via API).
- Create a signature request with user data and RAO identification (token or credentials).
- Upload documents (or, in hash flow, upload the hash JSON).
- Retrieve the service contract (PDF) so the user can view it before signing.
- Generate OTP (for Uanataca SMS) or use another authentication method.
- Call the sign endpoint with the OTP or external auth data.
- Retrieve signed documents (or signed P7M in hash flow).
- Delete documents from the Optimizer when no longer needed (recommended; the service does not delete automatically).
For step-by-step API details, see each workflow page and the API reference.
- Workflows overview — Index of all workflow types with links to detailed guides
- Webhooks — For async and VideoID status notifications
- API reference — Full endpoint specification