> ## Documentation Index
> Fetch the complete documentation index at: https://ahasend.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration Guides

> Step-by-step guides for sending transactional email from your framework, runtime, deployment platform, or AI coding tool with the AhaSend SDKs.

Each guide focuses on one framework, runtime, platform, or development tool and
shows the relevant server-side integration, credential boundary, and deployment
details. Framework guides cover sending and webhook verification where the
platform supports them; development-tool guides focus on grounding, review, and
sandbox testing.

Already have a mailer in your framework, such as Nodemailer or ActionMailer? Point it at the [SMTP relay](/docs/smtp) instead: four settings, no new code. If your stack is not covered here at all, the [Quickstart](/docs/quickstart) shows the plain REST API, which works anywhere.

## Start with Your Language

<CardGroup cols={2}>
  <Card title="Node.js SDK" icon="node-js" href="/docs/guides/nodejs-sdk">
    `@ahasend/sdk` gives you a typed client, automatic retries, idempotency keys, and webhook adapters for Express, Fastify, and Next.js.
  </Card>

  <Card title="Go SDK" icon="golang" href="/docs/guides/go-sdk">
    `ahasend-go` gives you a typed client, built-in retries and idempotency, and a Standard Webhooks verifier for any `net/http` router.
  </Card>
</CardGroup>

## Web Frameworks

<CardGroup cols={3}>
  <Card title="Express" icon="server" href="/docs/guides/express" />

  <Card title="Fastify" icon="server" href="/docs/guides/fastify" />

  <Card title="NestJS" icon="server" href="/docs/guides/nestjs" />

  <Card title="Next.js" icon="layer-group" href="/docs/guides/nextjs" />

  <Card title="Nuxt" icon="layer-group" href="/docs/guides/nuxt" />

  <Card title="SvelteKit" icon="layer-group" href="/docs/guides/sveltekit" />
</CardGroup>

Also covered: [Hono](/docs/guides/hono), [Koa](/docs/guides/koa), [ElysiaJS](/docs/guides/elysiajs), [Encore.ts](/docs/guides/encore), [Remix](/docs/guides/remix), [Astro](/docs/guides/astro), and [Vite](/docs/guides/vite).

## Go Frameworks

<CardGroup cols={3}>
  <Card title="Gin" icon="golang" href="/docs/guides/gin" />

  <Card title="Echo" icon="golang" href="/docs/guides/echo" />

  <Card title="Fiber" icon="golang" href="/docs/guides/fiber" />
</CardGroup>

Also covered: [chi](/docs/guides/chi) and [gorilla/mux](/docs/guides/gorilla-mux), plus [Azure Functions](/docs/guides/azure-functions) and [Cloud Run functions](/docs/guides/google-cloud-functions) for Go on serverless.

## Runtimes and Deployment

The SDK runs on Node.js, Deno, Bun, Cloudflare workerd, and Vercel Edge. These guides cover what each platform changes: where secrets live, how deploys work, and what to watch for.

<CardGroup cols={3}>
  <Card title="Bun" icon="bolt" href="/docs/guides/bun" />

  <Card title="Deno Deploy" icon="bolt" href="/docs/guides/deno-deploy" />

  <Card title="Cloudflare Workers" icon="cloudflare" href="/docs/guides/cloudflare-workers" />

  <Card title="AWS Lambda" icon="aws" href="/docs/guides/aws-lambda" />

  <Card title="Vercel" icon="cloud-arrow-up" href="/docs/guides/vercel" />

  <Card title="Railway" icon="train" href="/docs/guides/railway" />
</CardGroup>

## AI Development Tools

AI agents write email code quickly and invent APIs just as quickly. These guides show how to give each tool the verified AhaSend SDK as standing context, then check the result in sandbox mode before it can send anything real.

<CardGroup cols={3}>
  <Card title="Bolt.new" icon="bolt" href="/docs/guides/bolt-new" />

  <Card title="Claude" icon="robot" href="/docs/guides/claude" />

  <Card title="Cursor" icon="i-cursor" href="/docs/guides/cursor" />

  <Card title="GitHub Copilot" icon="github" href="/docs/guides/github-copilot" />

  <Card title="Lovable" icon="heart" href="/docs/guides/lovable" />

  <Card title="v0" icon="wand-magic-sparkles" href="/docs/guides/v0" />

  <Card title="Windsurf" icon="wind" href="/docs/guides/windsurf" />
</CardGroup>

## What Every Guide Assumes

<Steps>
  <Step title="A Verified Sending Domain">
    The `from` address must be on a domain you have verified. See [Domain Setup](/docs/domains) if you have not done this yet.
  </Step>

  <Step title="An API Key with Send Scope">
    Create one in the [dashboard](https://dash.ahasend.com/account/-/settings/api-keys) with the `messages:send:all` scope, or scope it to a single domain to limit the blast radius if it leaks. The guides read it from `AHASEND_API_KEY`, alongside `AHASEND_ACCOUNT_ID` and, for webhooks, `AHASEND_WEBHOOK_SECRET`.
  </Step>

  <Step title="Sandbox Mode for Testing">
    Add `sandbox: true` to any send request and the API validates and accepts it without delivering mail. Use `sandbox_result` to rehearse a bounce or a suppression. See [Sandbox Mode](/docs/send-api/sandbox).
  </Step>
</Steps>

## Reference

<CardGroup cols={2}>
  <Card title="API Reference" icon="code" href="/docs/api-reference">
    Every endpoint, parameter, and response, including the webhook event payloads.
  </Card>

  <Card title="CLI" icon="square-terminal" href="/docs/cli">
    Send test messages and forward webhook events to localhost from your terminal while building an integration.
  </Card>
</CardGroup>