Welcome to Notary Connect API
Welcome to the Notary Connect API — Snapdocs' integration solution for title and settlement companies to programmatically manage signing orders. With these APIs you can create and update orders, upload documents for the notary, track notary assignments, add comments, and download completed scanback documents.
The Notary Connect APIs use a simple token-based authentication model and support both JSON and XML response formats.
Getting your API key
Notary Connect API keys are provisioned by Snapdocs and tied to your company or a specific client (title office branch) within your company. To obtain an API key:
- Contact your Snapdocs Customer Success Manager and request a Notary Connect API key.
- Your CS contact will generate the key and securely share the token with you.
- Store the token securely — it grants full API access to orders under your company or client.
Your API token provides direct access to create and manage orders. Do not share it in client-side code, public repositories, or unencrypted channels. If you believe your token has been compromised, contact your Snapdocs Customer Success Manager immediately to have it revoked and reissued.
API key types
There are two types of API keys, which affect the scope of data you can access:
| Key Type | Scope | Notes |
|---|---|---|
| Company Key | Access to all orders, clients, and products across the entire company. | Can update order status (complete, cancel, etc.). Can specify client_id when creating orders. Can list comments. |
| Client Key | Access limited to orders, products, and team members for a single client (title office branch). | Must provide team_member_id when creating orders. Cannot update order status. Cannot list comments. |
Your CS contact will let you know which type of key you've been issued.
Environments
Use our Demo Environment as any customer starting your integration. Once the integration is complete, you can then switch to Production Environment.
| ENV | URL |
|---|---|
| Demo | https://app.cs-demo0.snpd.io/ |
| Production | https://app.snapdocs.com/ |
Base URL
All Notary Connect API requests should be made to:
https://app.cs-demo0.snpd.io/mobile_notary_api/v1/
Authentication
Every API request must include your API token in the X-AUTH-TOKEN HTTP header.
curl -X GET "https://app.cs-demo0.snpd.io/mobile_notary_api/v1/clients" \
-H "X-AUTH-TOKEN: your_api_token_here" \
-H "Content-Type: application/json"If the token is missing, invalid, or has been revoked, the API returns a 401 Unauthorized response with an empty body.
Response format
The API supports both JSON (default) and XML response formats. The format is determined by the configuration of your API key at provisioning time — not by request headers. Your CS contact can configure this when creating your key.
| Format | Content-Type | Notes |
|---|---|---|
json | application/json | Default format. Recommended for most integrations. |
xml | application/xml | For systems that require XML. Request bodies can be sent as XML with a root <order> element. |
Available endpoints
The Notary Connect API provides the following endpoints:
| Endpoint | Method | Description |
|---|---|---|
| List clients | GET | Retrieve clients with their products and team members. Use the returned IDs when creating orders. |
| List products | GET | Retrieve available signing products with detailed configuration (scanbacks, RON, witnesses, etc.). |
| Create order | POST | Create a new signing order with signer details, signing location, and product selection. |
| Get order | GET | Retrieve full order details including status, notary assignment, and attachments. |
| Update order | PUT | Update order fields such as appointment date, signer info, or signing location. |
| Update order status | PUT | Complete, cancel, hold, or reactivate an order. Company keys only. |
| Upload attachment | POST | Upload a document to an order (multipart or base64). |
| Download attachment | GET | Download a document attachment (redirects to a temporary download URL). |
| List comments | GET | Retrieve all non-internal comments on an order. Company keys only. |
| Create comment | POST | Add a comment to an order with visibility controls. |
Next steps
Follow the Integration Workflow guides to learn the recommended order of API calls:
- Discover your configuration — Retrieve clients, products, and team member IDs.
- Create orders — Create signing orders with signer details.
- Upload documents — Upload closing documents for the notary.
- Monitor orders — Track notary assignment and signing progress.
- Download & manage — Download scanbacks, update status, and add comments.
Also review the Errors guide for error handling details, and explore the API reference for full endpoint documentation.