Skip to content
Docs
Esc
  • OverviewGuidesWhat exists today, and where to start.
  • QuickstartGuidesKey, domain, first send — in that order.
  • AuthenticationGuidesBearer keys, the mandatory User-Agent, and what each refusal means.
  • ErrorsGuidesThe whole vocabulary, with the status each name carries.
  • IdempotencyGuidesRetry a send without sending it twice.
  • PaginationGuidesCursors are item IDs, not page numbers.
  • Rate limitsGuidesTen a second per team, and the headers that tell you where you are.
  • EventsGuidesEvery event a webhook can carry, with one real payload each.
  • DomainsGuidesThe records, where they go at each registrar, and what the page does while you wait.
  • TrackingGuidesOpens and clicks: one record, two toggles, and what an open really means.
  • TemplatesGuidesFifty-seven starters sorted by goal, and how to keep a campaign as a template.
  • ReceivingGuidesInbound mail, and the Inbox: a webhook fires, you read it, you answer it.
  • InboxGuidesChannels, personal mailboxes and seats: who sees what, and where a reply goes.
  • Mail appsGuidesComing soon: your Rasket address in Apple Mail, Outlook and the Gmail app.
  • Inbox APIGuidesOpen, read and answer support conversations from your app, with the same key.
  • Support inbox in your appGuidesA Contact us form that opens a conversation your team answers, in five minutes.
  • Replies to your emailsGuidesOne field on a send, and the customer's reply opens a conversation.
  • Let an agent triageGuidesAn AI agent reads, notes and drafts over MCP; a person sends.
  • Node SDKGuidesThe rasket package: typed from the API's own document, retries only what is safe.
  • Python SDKGuidesThe rasket package on PyPI: the Node client's methods, in snake_case, over httpx.
  • MCP serverGuidesConnect Claude, ChatGPT or any MCP client: your scopes, no key.
  • AI assistGuidesSubject lines, drafts and diagnosis — in the dashboard and over the API, off until you allow it.
  • AgentsGuidesLet an AI agent set Rasket up: the skill, the rules file, MCP, and the recipe they share.
  • OAuthGuidesLet another app act for a team: register, authorize with PKCE, exchange, refresh.
  • Single sign-onGuidesOIDC login for your team, a domain proved by DNS, enforcement and break-glass.
  • IntegrationsGuidesVercel, Netlify and Cloudflare, Zapier and n8n, a WordPress plugin, and Notion contacts.
  • SMTPGuidesSend from anything that speaks SMTP: settings, setup guides, limits and replies.
  • ZapierGuidesSend email, add contacts and react to email events from a Zap, with no code.
  • n8nGuidesThe Rasket node and trigger for n8n workflows: install, connect, every operation.
  • VercelGuidesAdd Rasket on Vercel: a Sending key in each project as RASKET_API_KEY, no copying.
  • WordPressGuidesThe Rasket plugin: every email your site sends, through Rasket, with a safe fallback.
  • NotionGuidesTurn a Notion database of people into contacts in a segment, once or every hour.
  • Migrating to RasketGuidesBring contacts, unsubscribes, lists and templates from Mailchimp, Klaviyo and more.
  • EmailsAPI referenceSend, batch, retrieve, list, reschedule, cancel, attachments.
  • DomainsAPI referenceAdd a domain, publish its records, verify it.
  • API keysAPI referenceCreate, list, rename and revoke credentials.
  • WebhooksAPI referencePayloads, signature verification, retries and replay.
  • SuppressionsAPI referenceAddresses we will not send to, and why.
  • LogsAPI referenceEvery request made with this team's credentials.
  • MetricsAPI referenceDelivery, bounce, complaint and engagement counts.
  • TemplatesAPI referenceVersioned email content with typed variables, addressed by ID or alias.
  • ContactsAPI referenceYour audience: contacts, their typed properties, segments and topic choices.
  • SegmentsAPI referenceAudiences defined by a filter, by hand, or both.
  • TopicsAPI referenceWhat contacts subscribe to, and the preference page's list.
  • CampaignsAPI referenceCampaigns, at /broadcasts: one message to a segment, from draft to results.
  • ImportsAPI referenceCSV uploads: column mapping, conflicts and counts.
  • AutomationsAPI referenceWorkflows that run per contact: the graph, its versions, and every run.
  • Custom eventsAPI referenceThe names your product fires, and what starts a workflow.
  • ReceivingAPI referenceMail sent to you: the message, its attachments, its raw source.
  • OAuthAPI referenceClient registration, the token endpoint, and the grants a team has given.
  • TeamAPI referenceThe team a credential belongs to: its plan, sender identity, AI flag and members.
  • BillingAPI referencePlan, usage, invoices and add-ons, and the hosted pages where a customer pays.
  • AI helpersAPI referenceSubject lines, a first draft, and why an email did what it did.
  • InboxAPI referenceChannels, conversations, messages, notes and search in your support inbox.
Documentation
Sign inGet started

GuidesInbox API

Inbox API

Your app already sends email through Rasket. The Inbox API lets it work the other half too: open support conversations, read them, reply, and hear about every change — from the same API and the same key.

Start here

Inbox API guides
GuideWhat it does
Add a support inbox to your appA Contact us form opens a conversation, in five minutes.
Route replies to your emailsOne field on POST /emails.
Let an agent triageMCP tools for Claude, Cursor and others.

What you can do

  • Open a conversation from your app — a Contact us form, an in-app message, a cancellation reason. It lands in a channel like support@, next to email.
  • Bring replies home — add inbox to an email you send, and when the customer replies it becomes a conversation linked to that email.
  • Read, reply and organise — list and search conversations, reply from the channel's address, add internal notes, assign, and set open, pending or done.
  • React to changes — six webhook events tell your server when something happens.

Every call is on the Inbox API reference, and the six events are on Events.

The pieces

Inbox API objects
ObjectWhat it is
ChannelA shared address your team answers, like support@lumen.app. The API only ever sees channels.
ConversationOne thread with a customer: their messages, your replies, internal notes, an assignee and a status.
MessageSomething the customer wrote (by email or through your app), or a reply your team sent.
NoteInternal. Never sent to the customer.

Keys and access

Inbox access is set on each API key, separately from what the key may send. Existing keys have none — a Full access key too. A team admin sets it in the dashboard under API keys, and can limit the key to some channels.

Inbox access levels
Inbox accessCan
NoneThe default. The key can't see the inbox.
Open conversations onlyCan create conversations and nothing else. Use it for a form.
ReadList, read and search.
Read and replyAlso reply, add notes, assign, and change status, labels and folders.

An AI agent or another app connects with OAuth instead, and acts as the person who connected it: inbox:read to read, inbox:write to write. See the MCP server.

Personal mailboxes are private to their person. No key, app or agent can reach them, and their IDs answer 404.

What it costs

Included with your Inbox seats. A conversation your app opens counts as received mail, which is free. Replies count as sends, like any other email.

Not yet

A chat widget you can drop into your site is planned separately.