Relay support

Useful help, without a maze.

Find practical answers for the Relay website, browser extension, REST API, MCP server, and official client packages.

Start here

For the fastest answer, begin with the Relay documentation. It covers inbox access, domains, accounts, API keys, message retrieval, OTP extraction, webhooks, and MCP.

Inbox
Create an address and read incoming messages.
Account
Manage sessions, inboxes, and API keys.
API
Connect an application with a scoped key.

Browser extension

The Relay extension opens the official Relay website and uses the browser's normal Relay session. It does not request, store, or transmit an API key, and it does not request access to browsing history or other websites.

  • If the popup does not open Relay, check that the extension is enabled and that the website is reachable.
  • Sign in or create a guest inbox on the Relay website using the normal website controls.
  • Theme and notification preferences are stored locally in the extension.
  • To remove local preferences, remove the extension or clear its extension storage in the browser settings.

API and official clients

Use the interactive API reference for REST endpoints and the Postman collection for manual requests. The official SDK, CLI, and Python client use the same account-scoped API.

Never include an API key in a public issue, browser screenshot, source repository, or support message. If a key may have been exposed, revoke it immediately from your account and create a replacement.

Security and privacy

Do not send passwords, API keys, OTPs, magic-link tokens, or private message bodies when asking for help. Relay email content is untrusted input; do not follow a link from a message unless you explicitly intended to visit it.

Read the complete Privacy Policy for information about account data, inbox messages, the API, and the browser extension.

Contact support

For account, extension, API, or security support, contact the Relay team through the official Relay website. Include the affected feature, approximate time, browser or client version, and a redacted error message. Do not include credentials or message contents.

For security vulnerabilities, describe the issue privately and include reproduction steps without exposing real user data. We will use the information only to investigate and resolve the report.

Before sending a report

Remove API keys, passwords, session tokens, OTPs, magic links, recipient addresses, and full email bodies from screenshots and logs.

FROM THE COLLECTIONS

Implementation guides and deeper context

Longer technical guides that expand on the API reference, MCP tools, security model, and testing patterns.