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

GuidesTemplates

Templates library

Start an email from one of fifty-seven designed starters, sorted by what the email is for, or keep a campaign you already sent as a template of your own.

Starters

Every starter is a drag-and-drop email that already wears your brand: your logo or name, your font and your footer. Pick one in the dashboard under Templates → Starters, or create a template with starter set to its slug. Either way you get a copy that is yours to edit. Changing the copy never changes the starter, and improving a starter never changes your copy.

Starter goals
GoalStartersFor
welcome6The first emails after a sign-up: a hello, a checklist, a tour, an offer.
launch6Something new: an announcement, a pre-order, a waitlist, release notes.
newsletter8Regular news: a magazine, a roundup, a letter, a product update.
winback5People who drifted off: a comeback offer, what changed, a question.
receipts6What someone bought: receipts, orders, shipping, invoices, renewals.
event5Webinars and meetups: the invite, the reminder, the recording.
promotion8Sales and offers: a flash sale, a season, a bundle, free shipping.
digest6Numbers and activity: a weekly summary, a monthly report, a year in review.
basics7Plain account and order emails: sign-in links, password resets, receipts.
  • Each starter also has a kind: campaign for a send to a segment, flow for an automation, transactional for a reply to something a person did. It is a suggestion. Any template can be sent any way.
  • Every link in a starter is a variable, like {{shop_url}}. Fill it when you send, or replace it with your own link in the editor.
  • If you saved a header or a footer for your project, a new copy uses yours in place of the starter's.

Saving a campaign as a template

A campaign that worked is worth keeping. Open it, or its row menu in Campaigns, and choose Save as template. You get a new, published template with the campaign's subject, HTML and plain text, exactly as they were. Saving twice makes two templates.

Merge variables such as {{{FIRST_NAME}}} and {{{UNSUBSCRIBE_URL}}} are kept. They fill in when the template goes out as a campaign again, not when it is sent as a single email.

From the API

  • GET /starters lists the library, and GET /starters?goal=welcome one goal of it. See Templates.
  • POST /templates with starter makes your copy of one.
  • POST /broadcasts/{id}/save-as-template keeps a campaign as a template. The key needs to write templates and read broadcasts. See Broadcasts.