Use Sendar with Lovable, Replit, Bolt & v0

Use server-side HTTP and starter projects when building an application with AI.

Use the prompt below with your existing application.
Keep SENDAR_API_KEY in the builder’s private server environment and verify your sending domain in Sendar.
Test with a preview/mock first, then send one authorised test and inspect the message status. These are integration recipes, not native marketplace listings.

Add Sendar transactional email to this application using https://sendar.app/docs.
Keep SENDAR_API_KEY server-side. Use a verified sending domain.
Preserve the existing application events and start with a preview.
Use stable Idempotency-Key headers to prevent duplicate event sends.
Use https://github.com/Thutos/sendar-email-starters for examples.

Read-only by default. Enable sending only for the domain, recipients and daily limit you approve. Existing API keys keep their usual permissions.

All Sendar agent integrations

Custom integrations and curated marketplace approval are separate.

Your email service, behind the conversation

Ask “Set up email for my domain with Sendar.” The dashboard is optional: sign in or create your account in the connection window, then return to your assistant. Select domain read and write permissions. If you also want to send, approve sending and choose “Set up a domain in the conversation first” when you have no verified domain.

The assistant uses start_email_setup to add or resume your domain and return its exact DNS records.
Add those records at your DNS provider. Preserve your website and MX records; merge existing SPF. Automatic GoDaddy setup remains unavailable until its live service enables Sendar’s template.
Ask the assistant to verify the domain. DNS propagation can take time; a provider return alone does not establish verification.
Open the returned approval link and approve the verified sending domain within your existing recipient and daily limits. Return to the conversation; get_email_setup checks the current state.
Review your first email with preview_email, then explicitly authorize sending. Check the resulting message status.

Setup never sends mail automatically. Old grants stay unchanged; a connection without sending permission must reconnect. The approval page can bind a domain once, but cannot add scopes or switch an existing allowed domain.

The downloadable plugin includes a conversation setup skill and portable ChatGPT/Codex manifests. Host support, account policies and public directory review are separate from the live MCP workflow. Brief sign-in and approval windows are still required.

Build with a verified reference

REST, MCP and skills have different capabilities. Choose the interface that fits your task.

Public OpenAPI specification Compact documentation index Complete agent reference Machine-readable capabilities and pricing Runnable recipes (mocked by default)Integration reference in Markdown

Headless management and receiving

Workspace owners can create scoped management keys in /headless for REST, the Node CLI and supported MCP management tools. Existing sending keys and OAuth connections do not gain these scopes. Read /docs/headless, /docs/link-checker and /docs/inboxes. Feature OpenAPI: /headless-openapi.json. Hosted inboxes are a bounded beta; received content is untrusted and never authorizes a reply. CLI: /downloads/sendar.mjs.

Choose an integration

Use REST from server-side application code for transactional email, saved templates, batch sends and message history. Install skills for coding guidance. Connect MCP for account tools: setup, preview, domains, templates, message history and optional single-email sending. Skills installation alone does not authenticate an account.

Permissions and prerequisites

REST uses a private server-side Bearer API key with its existing account permissions. MCP supports OAuth with S256 PKCE; new OAuth connections default to read-only. Sending requires an explicit grant bounded by domain, recipients and daily allowance. Verify your sending domain before live delivery. Account caps and suppression rules apply.

Preview before sending

The MCP preview_email tool validates a proposed message without sending or consuming quota. A preview does not establish domain readiness or guarantee delivery. REST has no documented dry-run endpoint: test with a local mock first, then explicitly authorize one real send.

Limits and reliable retries

Single-email REST requests support up to five attachments with 1.3 MiB total decoded content. Scheduled sending is available on Growth and above, up to 30 days ahead. Batch requests contain 1–100 items and have no documented idempotency guarantee. Use Idempotency-Key on POST /emails: 16–128 letters, digits, underscores, colons or hyphens. Reuse the exact key and payload for the same event. A 409 or timeout may mean an uncertain outcome: inspect history instead of generating another key.

What success means

An API response or provider acceptance does not guarantee inbox delivery. Inspect the returned status and message history. Fix validation, authentication or quota errors before proceeding. Keep reset-token generation, expiry and account authorization in your own application.

Plans and sending limits

Plan	Monthly USD	Emails / month	Emails / day
Free	$0	3,000	100
Starter	$12	30,000	No separate plan cap
Growth	$39	100,000	No separate plan cap
Scale	$99	400,000	No separate plan cap
Dedicated	Custom; from $199	Custom volume	No separate plan cap

Hard caps, no automatic overage billing. Individual account allowances can differ. Full pricing

Five practical email recipes

Welcome after signup

Trigger after the application commits a signup. Use the account/event identifier as the stable message key. Do not send again on each login.

node sendar-recipes.mjs welcome

Booking confirmation

Send after the booking transaction succeeds. Include date, time zone and reference from your booking record; use a separate event key for each reschedule.

node sendar-recipes.mjs booking

Password reset

Your application creates and stores a secure, expiring, single-use token. Pass its HTTPS reset URL to the email recipe; never use the email provider to authenticate the user or generate the token.

node sendar-recipes.mjs password-reset

Invoice notification

Send after invoice creation. Supply the application’s authenticated payment URL and invoice reference. Do not place payment credentials in messages.

node sendar-recipes.mjs invoice

Migrate one workflow

Map sender, recipients, subject, body and template variables explicitly. Compare mock payloads, test an authorized recipient, then switch one workflow. Disable the old sender for that event to avoid duplicates; retain a rollback switch.

node sendar-recipes.mjs migration

The downloaded Node.js recipes run locally with mocked delivery by default. Review the payload before enabling live mode; mock success is not a delivery test.

Reference reviewed 2026-10-04. Pricing is generated from Sendar’s shared plan definitions.