Prerequisite
To access T-RSSP through the RESTful API, you need a suitable User account and an API key. A User can generate a unique API key to identify your application. Authentication utilizes the User and the associated API key to generate an OAuth 2.0 bearer token, which is then required for authorization in all API calls.
Contact Us for Demo: Click the 'Contact Us' button, and you will be redirected to support@idthrivo.com. Reach out to ThrivoSign support to arrange a personalized demonstration.
Access Demo Server: Click the 'Access Demo Server' button, and you will be redirected to the demo server link. Explore the features and functionalities of ThrivoSign in a simulated environment.
Create an User account:
The business application must connect to the account and make JSON requests to manage signing users/recipients.
Use the ThrivoSign cloud service for testing by creating a free user account.
Once completed, you can immediately log in to the system and utilize all available features within the ThrivoSign application.
Create an API Key:
Set an Application Name and Call-back URL, then generate an API Key in ThrivoSign using the Enterprise Settings menu > Integrations screen.
Note the Application Name and API Key.
Create Workflow Templates (Optional):
Define the location of each signature field and the expected signing user in the workflow template.
Specify other document and workflow control options, such as PDF permissions.
Templates may enhance efficiency, especially for frequently used standard contracts or agreements.
ThrivoSign also supports dynamic creation of signature fields for real-time document creation.
Understand the signature you need—basic electronic or digital. With ThrivoSign, digital signatures mean each person must have an account. For simpler stuff, electronic signatures work without needing an account for everyone. Coding depends on the signature type, and tight or loose integration decides if users log in to ThrivoSign.
Last updated