# White-labeling with WaiverStevie

White label Image

On WaiverStevie's enterprise plan you can offer our eSignature features within your own platform! This includes:

  • Allowing your customers to create documents right on your site.
  • Providing an embedded version of the WaiverStevie annotation tool.
  • Sending signature requests via email OR creating signature requests and distributing the links on your own.
  • Tracking your customers' signed PDFs, and presenting these documents on your page.

# First steps: authentication

Short lived tokens allow you to delegate WaiverStevie functionality to your customers. If you are an approved enterprise client, you may use the white-label endpoint to fetch a 64 character token; you will need your API key to make the request. The token will expire within 20 minutes of it's first usage, so we recommend requesting a new token at each stage in the document life cycle.

These tokens will be scoped to a domain and only browser requests from that origin will be accepted.

# PDF upload delegation

The entire process for uploading a PDF on behalf of a customer is simple:

  1. Request a new white-label token using your API key. We recommend that you pass along a end_user_id parameter in this request. The end_user_id may be any string or number shorter than 64 digits. This will allow you to segment your clients' documents from each other. All documents fetched with a scoped white-label token will have been created by that same end_user_id.
  2. Within your client code, make a POST request to our upload-document endpoint. This multipart request should contain a form key with mime-type PDF. WaiverStevie will return the document id.

# Annotating from your application

When your customer is ready to annotate their document, i.e. prepare it to be signed, you

  1. (Recommended) request a new white-label token when your user chooses to annotate the document. Remember to pass an end_user_id if the
  2. Embed an iframe into your application that uses the following source: https://<YOUR_SUBDOMAIN>.waiverstevie.com/documents/:doc_id/annotate?white-label=<WHITE_LABEL_KEY>. If you don't have a custom subdomain yet, reach out to WaiverStevie support at info@waiverstevie.com.
  3. The embedded site will handle all of the annotating and saving points!

# Sending signature requests

See our standard API docs for sending eSignature requests.

White-label clients can optionally pass an end_user_id when sending a signature request; this will ensure that the client can only send their own documents.

# Tracking signature requests

See our standard API docs for fetching eSignature requests, complete or incomplete. Again, you may filter by end_user_id, fetching only documents of a specific end user.

# Webhooks

If you would like to receive active notifications via webhook when a form is signed, pass a webhook_url to the document creation API call. For example, you might pass the same endpoint for all documents of a specific end_user_id.

# Support

WaiverStevie is in the process of migrating our manual, internal white-label integration into a simple standard. If you have any questions integrating please send a message to info@waiverstevie.com. We typically respond within a day. We also have developers available for hire to help you build your integrations.