The PactSafe Developer Hub

Welcome to the PactSafe developer hub. You'll find comprehensive guides and documentation to help you start working with PactSafe as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Guides

Getting Started

Hi there! Welcome to PactSafe's Developer Portal. We have a rich set of developer tools to help you easily integrate our legal system of record into your own apps.

We have 3 options to easily integrate your environment:

  • Our JavaScript Library
  • Our Activity API
  • Our REST API

Our JavaScript Library

What is it?

The JavaScript library is designed to be as seamless and straightforward as possible to get PactSafe integrated, to start tracking who accepted important legal terms, and get back to innovating!

When should I use it?

You should be using our JavaScript library when you're plugging us into your website and web app. This would include ecommerce, your SaaS app, and more.

Where do I learn more?

Our Activity API

What is it?

Our Activity API is a legal microservice located at that was built from the ground up to support the functionality behind our JavaScript library. It has 3 calls:

  1. latest returns a JSON object set of Contract IDs and boolean true/false values based on whether or not a signer has accepted the latest versions of a Group of Contracts.
  2. retrieve returns a JSON object set of Contract IDs and Version IDs to tell you which versions your signer has accepted.
  3. send will send us Contract IDs and Version IDs (as well as signer information and site Access ID) to track who's accepted what.

When should I use it?

Generally, customers will use our Activity API directly when you have a strong preference of not using JavaScript on your site, or you have a specific need to retrieve information on a user outside the context of a form on a page.

For example, if you have a persistent session in your web app you can call the following to determine whether or not to show a clickwrap agreement to a user:

GET[email protected]&sid=ACCESS_ID&gkey=register-clickwrap

That call would return:


Where do I learn more?

Read up more on our Activity API here.


What is it?

Our REST API is a comprehensive set of APIs to connect to PactSafe for things like creating or versioning contracts, updating user information, sending contracts manually, and more.

When should I use it?

Our entire user interface is built on top of our REST API, so any function besides the simple latest, retrieve, and send calls of our Activity API will require our REST API.

Here are some examples for when you'd want to use our API:

  • You need to retrieve the content of a Contract stored in PactSafe.
  • You want to send a Contract to an individual for electronic signature.
  • You want to retrieve or update metadata about a contract like tags, name, or description.
  • You want to update a user's login details.
  • You want to retrieve detailed activity for a signer.

Where do I learn more?

Check out our REST API docs for more information. There are a lot of amazing resources to help you get started–including sample code, the API explorer, and more.

Who is PactSafe? PactSafe is a secure contract management platform, the world's fastest electronic signature, and contract analytics solution for business contracts, web and mobile apps, and other contracts that are executed online with your customers. The Vault Developer Toolkit provides you tools to plug in to your websites or mobile apps to help your business unify signatures across all your contracts.

The REST API exposes CRUD operations on all of the core PactSafe resources. We follow conventional REST methods and protocols using POST (create), GET (retrieve), PATCH (update), and DELETE (delete).

All data is sent and received as JSON, and all requests require an OAuth Access Token for authorization. An OAuth Access Token can be created for your user by creating one in your account.

Updated 22 days ago

Getting Started

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.