Keep every product and client apart

# The projects your key can see. A key belongs to one project.
curl https://api.mailbay.dev/v1/projects \
  -H "Authorization: Bearer $MAILBAY_API_KEY"

# {"data": [{"id": "prj_01jc...", "name": "Superchat", "slug": "superchat", ...}]}

# Making a new project, inviting teammates, reading the audit log and
# exporting need you signed in (dashboard), not an API key:
#   POST /v1/projects   {"name": "Invoicely"}

# Sending only, and only from one domain
curl -X POST https://api.mailbay.dev/v1/keys \
  -H "Authorization: Bearer $MAILBAY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "web app", "permissions": "sending", "domain_id": "dom_01jc..."}'

# Reading and replying in one inbox only
curl -X POST https://api.mailbay.dev/v1/keys \
  -H "Authorization: Bearer $MAILBAY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "support bot", "permissions": "inbox", "inbox_id": "ibx_01jc..."}'

# The secret is shown once in the reply. Sukhovei Mail keeps only a hash.

In the dashboard, under Settings:

  Members   Invite by email. Choose a workspace role, and for a Member,
            a role in each project and (optionally) which inboxes.
  Audit log Who did what and when: keys, domains, members, projects.
  Export    Download everything in the workspace as one file.

The same things over the API (signed in):

  POST  /v1/invitations
  {"email": "sam@acme.com", "workspace_role": "member",
   "projects": [{"project_id": "prj_01jc...", "role": "support"}]}

  GET   /v1/audit
  GET   /v1/workspace/export
  PATCH /v1/workspace/retention   {"retention_days": 90}