Introduction

Maylee connects Gmail, Microsoft 365 and IMAP mailboxes in one workspace, and sorts them with AI. This site documents the two ways to drive a workspace from outside the app:

The REST APICopy Anchor Link

Base URL        https://api.maylee.app/api/v1
Authentication  Authorization: Bearer mk_...
Content type    application/json

The machine-readable reference is the OpenAPI document, also served without authentication on GET https://api.maylee.app/api/v1/openapi.json, so that you can generate a client before you even have a key.

QuickstartCopy Anchor Link

1. Create an API keyCopy Anchor Link

In the Maylee app, open Settings, then API keys, and create a key in the Maylee API Key section. Give it the read scope for this quickstart. The secret starts with mk_ and is shown once: copy it now. See Authentication for scopes and the separate permission to send emails.

export MAYLEE_KEY="mk_..."

2. List your mailboxesCopy Anchor Link

Every request carries the key as a Bearer token. The workspace comes from the key: no URL carries a workspace identifier.

curl https://api.maylee.app/api/v1/mailboxes \
  -H "Authorization: Bearer $MAYLEE_KEY"

{
  "items": [
    {
      "id": "cmbx1a2b3c4d5e6f7g8h9i0j",
      "email": "contact@your-company.com",
      "name": "Contact",
      "picture": null,
      "provider": "GOOGLE",
      "isActive": true,
      "createdAt": "2026-06-02T09:14:31.000Z",
      "lastSyncAt": "2026-08-25T14:02:11.000Z",
      "syncError": null,
      "backwardSyncComplete": true
    }
  ]
}

Keep the id: sending needs a mailboxId, and most filters use it.

3. Read the latest emailsCopy Anchor Link

curl -G https://api.maylee.app/api/v1/emails \
  -H "Authorization: Bearer $MAYLEE_KEY" \
  --data-urlencode 'mailboxId=cmbx1a2b3c4d5e6f7g8h9i0j' \
  --data-urlencode 'folderType=INBOX' \
  --data-urlencode 'limit=10'

You get a page of emails, most recent first, with sender, recipients, subject, preview snippet and labels. Bodies are fetched on demand with GET /emails/{emailId}/body. Continue with Common tasks to reply in a thread, prepare a draft for review, or let Maylee classify email for you.

Five things to knowCopy Anchor Link

The workspace comes from the key, never from the URL. A key only reaches the data of the workspace it was created in, even if the URL is forged.

Session cookies are never accepted on /api/v1. Only Authorization: Bearer mk_... works, which makes the API immune to cross-site request forgery.

The secret of a key is shown once, at creation. Only a SHA-256 hash of it is stored: if you lose it, create a new key.

Making email leave the workspace needs two permissions: the write scope and the Send emails option of the key. That covers sending, auto-forward rules and auto-reply. A key that classifies email should not be able to write to your customers if it leaks.

Every request is bounded. Requests per minute and per month, filter complexity, execution time and body size all have limits, and every authenticated response carries X-RateLimit-* headers. See Rate limits and quotas.

For AI agentsCopy Anchor Link

This documentation is written to be read by agents too. Every page is available as Markdown: add .md to its URL, or send Accept: text/markdown. /llms.txt lists every page with a one-line summary, and /llms-full.txt holds the whole site, API reference and MCP tools included, in one file.