# Smarsh API: access, auth, sandbox and MCP (checked Oct 2026)

> Smarsh publishes an overview of its V3 REST APIs for communications capture, search, export and supervision, but access is limited to customers and approved partners. Authentication is OAuth 2.0 client credentials provisioned through a Smarsh representative, and the detailed documentation sits behind a login.

- Vendor: Smarsh (Smarsh)
- Website: https://www.smarsh.com/
- Category: Compliance and archiving (core)
- API access: Partner-gated
- Last checked: 2026-10-17
- Id: `smarsh` · JSON: https://wealthtech.dev/products/smarsh.json

## Developer surface

| Field | Value | Source and quote | Checked |
|---|---|---|---|
| API access | Partner-gated | Checked on the source's own page. [www.smarsh.com](https://www.smarsh.com/platform/developers/) "API access is available to Smarsh customers and approved partners." | 2026-10-17 |
| Developer docs | https://www.smarsh.com/platform/developers/ | Checked on the source's own page. [www.smarsh.com](https://www.smarsh.com/platform/developers/) "Connect Your AI Workflows With Smarsh APIs" | 2026-10-17 |
| API style | REST | Checked on the source's own page. [www.smarsh.com](https://www.smarsh.com/platform/developers/) "All V3 APIs follow RESTful conventions and use OAuth 2.0 Client Credentials with short-lived JWT bearer tokens." | 2026-10-17 |
| Authentication | OAuth 2.0 (client credentials) | Checked on the source's own page. [www.smarsh.com](https://www.smarsh.com/platform/developers/) "Smarsh APIs use OAuth 2.0 Client Credentials to provide secure, service-to-service access without individual user sign-ins." | 2026-10-17 |
| How to get access | Contact your Smarsh representative to have OAuth 2.0 client credentials provisioned for your organization. | Checked on the source's own page. [www.smarsh.com](https://www.smarsh.com/platform/developers/) "Contact your Smarsh representative to have OAuth 2.0 client credentials provisioned for your organization." | 2026-10-17 |
| Sandbox | Not found | Not found. The developer page says 'test the available endpoints' but names no sandbox or test environment. Detailed API documentation at https://docs.smarsh.com/apidocs/v3-apis-1 and /apidocs/data-management-search redirects to a Smarsh Employee/Customer login page, so it was not read. The developer page says 'test the available endpoints' but names no sandbox or test environment. Detailed API documentation at https://docs.smarsh.com/apidocs/v3-apis-1 and /apidocs/data-management-search redirects to a Smarsh Employee/Customer login page, so it was not read. | 2026-10-17 |
| Rate limits | Couldn't read automatically | Couldn't read automatically. Not stated on the public developer page. Detailed API documentation at https://docs.smarsh.com/apidocs/v3-apis-1 and /apidocs/data-management-search redirects to a Smarsh Employee/Customer login page, so it was not read. Not stated on the public developer page. Detailed API documentation at https://docs.smarsh.com/apidocs/v3-apis-1 and /apidocs/data-management-search redirects to a Smarsh Employee/Customer login page, so it was not read. | 2026-10-17 |
| Webhooks | Couldn't read automatically | Couldn't read automatically. Not stated on the public developer page. Detailed API documentation at https://docs.smarsh.com/apidocs/v3-apis-1 and /apidocs/data-management-search redirects to a Smarsh Employee/Customer login page, so it was not read. Not stated on the public developer page. Detailed API documentation at https://docs.smarsh.com/apidocs/v3-apis-1 and /apidocs/data-management-search redirects to a Smarsh Employee/Customer login page, so it was not read. | 2026-10-17 |
| SDKs | Couldn't read automatically | Couldn't read automatically. No SDKs named on the public developer page. Detailed API documentation at https://docs.smarsh.com/apidocs/v3-apis-1 and /apidocs/data-management-search redirects to a Smarsh Employee/Customer login page, so it was not read. No SDKs named on the public developer page. Detailed API documentation at https://docs.smarsh.com/apidocs/v3-apis-1 and /apidocs/data-management-search redirects to a Smarsh Employee/Customer login page, so it was not read. | 2026-10-17 |
| OpenAPI spec | Couldn't read automatically | Couldn't read automatically. Not linked from the public developer page; the documentation site requires a login (redirect to identity.document360.io). Whether a spec exists behind the login was not checked. Not linked from the public developer page; the documentation site requires a login (redirect to identity.document360.io). Whether a spec exists behind the login was not checked. | 2026-10-17 |
| Partner program | https://www.smarsh.com/partners | Checked on the source's own page. [www.smarsh.com](https://www.smarsh.com/partners) "Join the Smarsh Partner Program now or sign in to your account on the partner portal." | 2026-10-17 |
| Public integration list | https://www.smarsh.com/partners | Checked on the source's own page. [www.smarsh.com](https://www.smarsh.com/partners) "View our partner directory to find one of the referral, reseller, alliance, technology, or consulting partners in our partner ecosystem." | 2026-10-17 |
| Ways to connect | Native API | Checked on the source's own page. [www.smarsh.com](https://www.smarsh.com/platform/developers/) "Capture, search, export, and retrieve communications data programmatically with metadata and chain-of-custody support." | 2026-10-17 |

## MCP servers and AI connectors

None recorded on public pages we checked.

## What the docs don't say

- The public developer page lists the V3 API families (Data Acquisition, Search, Export, Data Retrieval, Participant, Reconciliation, Audit Log, Case, Surveillance, Analytics, Ingestion) but not their endpoints, rate limits, webhooks or sandbox.
- The documentation links on the developer page lead to a login, so no endpoint detail is public.

## Changes

No changes recorded since this record was first published.
---
Source: https://wealthtech.dev/products/smarsh · Facts licensed CC BY 4.0 (attribution "wealthtech.dev"). Every fact states where it was checked and when; check the source before relying on it.