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

> Global Relay publishes docs for four archiving APIs (conversation, event, voice, email) that send communications data into its archive. Credentials are issued by an implementation engineer after enrollment, auth is OAuth 2.0 client credentials, and the Conversation Archiving API is limited to 1000 requests per minute on /conversations and 200 on /files.

- Vendor: Global Relay Communications Inc. (Global Relay Communications Inc.)
- Website: https://www.globalrelay.com/
- Category: Compliance and archiving (core)
- API access: Open docs, keys by approval
- Last checked: 2026-10-17
- Id: `global-relay` · JSON: https://wealthtech.dev/products/global-relay.json

## Developer surface

| Field | Value | Source and quote | Checked |
|---|---|---|---|
| API access | Open docs, keys by approval | Checked on the source's own page. [developers.globalrelay.com](https://developers.globalrelay.com/api/conversation-archiving-api/tutorials/getting-started/) "Before you can start calling the Conversation Archiving API, you must register your application and specify the data types you plan to archive." | 2026-10-17 |
| Developer docs | https://developers.globalrelay.com/api/conversation-archiving-api | Checked on the source's own page. [developers.globalrelay.com](https://developers.globalrelay.com/api/conversation-archiving-api/) "Protect the fidelity of conversations by using the Conversation Archiving API to programmatically send your data to the Archive." | 2026-10-17 |
| API style | REST | Checked on the source's own page. [developers.globalrelay.com](https://developers.globalrelay.com/api/conversation-archiving-api/tutorials/getting-started/) "All Global Relay API endpoints require HTTPS and conform to HTTP/1.1." | 2026-10-17 |
| Authentication | OAuth 2.0 (client credentials) | Checked on the source's own page. [developers.globalrelay.com](https://developers.globalrelay.com/api/conversation-archiving-api/) "The Conversation Archiving API uses the Client Credentials OAuth 2.0 grant type" | 2026-10-17 |
| How to get access | Enroll your application, including the data type to archive, by contacting your Global Relay Implementation engineer; they provide the client credentials. | Checked on the source's own page. [developers.globalrelay.com](https://developers.globalrelay.com/api/conversation-archiving-api/) "Enroll your application, including the data type you plan to archive, by contacting your Global Relay Implementation engineer" | 2026-10-17 |
| Sandbox | Yes, on request | Checked on the source's own page. [www.globalrelay.com](https://www.globalrelay.com/partners/become-a-technology-integration-partner/) "Work with our engineers in a dedicated environment to develop, test, and showcase your integration." | 2026-10-17 |
| Rate limits | Conversation Archiving API: 1000 requests per minute for /conversations and 200 per minute for /files. | Checked on the source's own page. [developers.globalrelay.com](https://developers.globalrelay.com/api/conversation-archiving-api/tutorials/getting-started/) "API calls are limited to 1000 requests per minute for the /conversations endpoint, and 200 per minute for the /files endpoint." | 2026-10-17 |
| Webhooks | Not found | Not found. No webhooks found on the Conversation Archiving overview, getting-started, API reference or Event Archiving overview pages. No webhooks found on the Conversation Archiving overview, getting-started, API reference or Event Archiving overview pages. | 2026-10-17 |
| SDKs | None stated | Checked on the source's own page. [developers.globalrelay.com](https://developers.globalrelay.com/api/conversation-archiving-api/tutorials/getting-started/) "Because the Conversation Archiving API is HTTP-based, it works with any language that has an HTTP library." | 2026-10-17 |
| OpenAPI spec | Published | Checked on the source's own page. [developers.globalrelay.com](https://developers.globalrelay.com/api/conversation-archiving-api/tutorials/getting-started/) "You can refer to the API Reference for the complete OpenAPI specification." | 2026-10-17 |
| Partner program | https://www.globalrelay.com/partners/become-a-technology-integration-partner | Checked on the source's own page. [www.globalrelay.com](https://www.globalrelay.com/partners/become-a-technology-integration-partner/) "Join our growing community of partners through Global Relay’s technology partner ecosystem to access an industry-leading Open Connector API platform." | 2026-10-17 |
| Public integration list | Not found | Not found. No public list of integrations or connectors found on the developer site or partner page read. No public list of integrations or connectors found on the developer site or partner page read. | 2026-10-17 |
| Ways to connect | Native API | Checked on the source's own page. [developers.globalrelay.com](https://developers.globalrelay.com/api/conversation-archiving-api/) "Transforming conversation data into files and archiving via SFTP or SMTP transfers is time-consuming and error-prone." | 2026-10-17 |

## MCP servers and AI connectors

None recorded on public pages we checked.

## What the docs don't say

- The four APIs listed on the developer site (Conversation, Event, Voice, Email) are all archiving APIs for sending data in; no API for reading data back out is listed.
- The API reference lists only a Production base URL; the sandbox mention is on the partner program page.
- Webhooks and SDKs are not mentioned on the pages read.

## Changes

No changes recorded since this record was first published.
---
Source: https://wealthtech.dev/products/global-relay · 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.