Esignature API Best Practices
We know esignatures can be confusing. That’s why we’re here to help. With PactSafe you’ll have everything you need to make your API run as efficiently as possible. Before you get started with this page it might be helpful to check out our esignature API overview [here](link to overview page). Moving on:
In order to start using PactSafe’s esignature API you’ll need an access token. Our REST API requires a valid OAuth 2.0 token, Why do you need this? It helps keep everyone safe! Our biggest priority is keeping your contracts secure. That’s why you’ll have access to the PactSafe Vault and why every REST call you make to PactSafe must have an authorization header to get the data you need. Your esignature API uses this constantly and setting it up is easy! For more on that check out this step-by-step guide.
Last but not least! Our esignature API has one more trick to optimize the way you use it. Publishing your first contract will open up the API for full use. Why do you need to publish a contract first? If you publish a public contract you’ll get your first group to go along with it. From there you can get your group id, send contracts, create new groups, and use all sorts of other customizable features to get our esignature API working for you.
That’s all you need to do to for the best esignature API experience ever. Just three easy steps.