Global Relay API
Global Relay Communications Inc. · Compliance and archiving · www.globalrelay.com
Open docs, keys by approval Last checked Oct 17, 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.
Developer surface
Open any row to see the page it came from, the exact words on that page and when we checked. "Not found" means we looked on the public pages listed in the note and the fact wasn't there.
| API access | Open docs, keys by approval Checked on the source's own page · Oct 17, 2026“Before you can start calling the Conversation Archiving API, you must register your application and specify the data types you plan to archive.”
|
|---|---|
| Developer docs | developers.globalrelay.com Checked on the source's own page · Oct 17, 2026“Protect the fidelity of conversations by using the Conversation Archiving API to programmatically send your data to the Archive.”
|
| API style | REST Checked on the source's own page · Oct 17, 2026“All Global Relay API endpoints require HTTPS and conform to HTTP/1.1.”
|
| Authentication | OAuth 2.0 (client credentials) Checked on the source's own page · Oct 17, 2026“The Conversation Archiving API uses the Client Credentials OAuth 2.0 grant type”
|
| 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 · Oct 17, 2026“Enroll your application, including the data type you plan to archive, by contacting your Global Relay Implementation engineer”
|
| Sandbox | Yes, on request Checked on the source's own page · Oct 17, 2026“Work with our engineers in a dedicated environment to develop, test, and showcase your integration.”
|
| Rate limits | Conversation Archiving API: 1000 requests per minute for /conversations and 200 per minute for /files. Checked on the source's own page · Oct 17, 2026“API calls are limited to 1000 requests per minute for the /conversations endpoint, and 200 per minute for the /files endpoint.”
|
| Webhooks | Not found Not found · Oct 17, 2026
|
| SDKs | None stated Checked on the source's own page · Oct 17, 2026“Because the Conversation Archiving API is HTTP-based, it works with any language that has an HTTP library.”
|
| OpenAPI spec | Published Checked on the source's own page · Oct 17, 2026“You can refer to the API Reference for the complete OpenAPI specification.”
|
| Partner program | www.globalrelay.com Checked on the source's own page · Oct 17, 2026“Join our growing community of partners through Global Relay’s technology partner ecosystem to access an industry-leading Open Connector API platform.”
|
| Public integration list | Not found Not found · Oct 17, 2026
|
| Ways to connect | Native API Checked on the source's own page · Oct 17, 2026“Transforming conversation data into files and archiving via SFTP or SMTP transfers is time-consuming and error-prone.”
|
MCP servers and AI connectors
None recorded. We found no MCP server or AI connector for Global Relay on the public pages we checked. See all MCP servers.
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 (Oct 17, 2026). Changes show up here and in the changelog.
Other compliance and archiving tools
COMPLY (Comply for RIA, formerly RIA in a Box)
Not found
Docupace
Partner-gated
Smarsh
Partner-gated
Something wrong or out of date? Send a correction. We change facts only on public evidence.