NotaryLive API - Getting Started

Page last updated: July 20, 2026

Getting Started with IPEN

Welcome to the NotaryLive IPEN API documentation!
This documentation is intended for Business Account partners who wish to create In-Person Electronic Notarization (IPEN) orders for their own notaries from their own services.

With IPEN, the signing happens face-to-face: your notary meets the signer(s) in person and the documents are signed and digitally sealed on the notary's device. The IPEN API lets you prepare these sessions ahead of time — uploading the documents, listing the participants, and assigning the notary — so your notary only has to open the session link and meet the signers.

Below you will find a list of API endpoints and their respective documentation.

Please note: All API calls must be made over HTTPS. All API calls must be authenticated using HTTP Basic Authentication. All API calls must be made with the Content-Type header set to application/json unless otherwise specified.


Requirements

Before you can create IPEN orders through the API, you will need:

  • A NotaryLive Business Account organization
  • At least one notary in your organization who has been approved for IPEN
  • IPEN-specific API credentials

Please contact us at support@notarylive.com to activate IPEN for your notaries. You can generate your own IPEN API keys in your NotaryLive dashboard under the IPEN API tab.
Please note: RON, eSign and IPEN use different API credentials. You cannot use your RON or eSign API credentials for IPEN API calls and vice versa.


Endpoints

The following is a list of our IPEN API endpoints and their respective documentation:

Endpoint Method Description
/api/v1/ipen/create POST Creates a new IPEN order
/api/v1/ipen/status GET Gets the status of an IPEN

Sandbox Environment

IPEN sandbox credentials let you test your integration without being billed — orders created with sandbox credentials are marked as sandbox orders and are excluded from your monthly invoice. The final "notarized" document produced by a sandbox session is watermarked and cannot be used as a real notarization.

Please note: Unlike our RON and eSign APIs, the IPEN API does not offer universal testing credentials, because every IPEN order must be assigned to an IPEN-approved notary in your organization. You can generate IPEN sandbox keys in your NotaryLive dashboard under the IPEN API tab, but you will also need at least one IPEN-approved notary before you can create test orders — please contact us at support@notarylive.com to activate IPEN for your notaries.


Moving to Production

Once you’re ready to go live, contact our team at support@notarylive.com to request production credentials. Replace your sandbox keys with your assigned production credentials.


Troubleshooting

  1. Verify your IPEN API credentials (username/password).
  2. Ensure requests are made over HTTPS.
  3. Confirm the correct Content-Type header.
  4. Confirm the notary you are assigning belongs to your organization and has been approved for IPEN.

If issues persist, please contact support@notarylive.com with your request payload and response for debugging assistance.


Copyright © 2026, NotaryLive.com