Skip to main content
Slate is the infrastructure layer that keeps accounts synced, documents compliant, and workflows running between creditors and their law firms. This documentation covers every public API you need to integrate with Slate — from syncing your account inventory and uploading evidence files to triggering e-signatures, running automated redaction, and managing quality control.

Introduction

Learn what Slate does and how the APIs fit together

Authentication

Get your bearer token and make your first authenticated request

API Reference

Full reference for every endpoint — Accounts, Files, Signatures, QC, and more

Guides

Step-by-step walkthroughs for common integration scenarios

What You Can Build

Slate exposes five API domains. Each one handles a distinct stage of the legal recovery lifecycle.

Accounts API

Sync your account inventory via upsert, and manage creditors, firms, and entities — keep Slate’s view of every account in step with your system of record

Files & Requests API

Upload files, create evidence and claims requests with exhibits, apply redactions, and run bulk downloads

Signatures API

Create e-signature and e-notary requests, get signing URLs, and track status

Quality Control API

Build configurable QC checklists and manage approve/reject review workflows

Users API

Manage the people and service credentials that interact with Slate, including notaries and affiants

Get Up and Running

1

Obtain your credentials

Contact your Slate account manager to receive your owner code and bearer token.
2

Make your first request

Call GET https://api.slate.inc/accounts/v1/accounts?owner=<owner-id> with your token to verify connectivity and retrieve your account list.
3

Sync your accounts

Use POST https://api.slate.inc/accounts/v1/accounts to upsert your account inventory. Slate matches on your crid and assigns each account a stable accountId (UUID) that you use for all subsequent operations.
4

Explore the workflows

Upload files, create document requests, trigger redaction, or initiate signature transactions — each workflow builds on the accounts you’ve synced.
All API requests are scoped to your owner (organization) and must include a valid bearer token. See Authentication for details.