> For the complete documentation index, see [llms.txt](https://kasplo.gitbook.io/kasplo-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kasplo.gitbook.io/kasplo-doc/channels/transactional-api-smtp/amp-email.md).

# AMP Email

### AMP Email Support via SMTP & API

Kasplo supports sending AMP (Accelerated Mobile Pages) emails through both SMTP and Email API, allowing you to deliver rich, interactive experiences directly inside the inbox — such as carousels, forms, accordions, and live data updates.\
AMP emails are supported by major ISPs including Gmail, Yahoo Mail, and [Mail.ru](http://mail.ru/), but require domain-level approval before you can start sending.

### Why Use AMP Emails?

* Embed dynamic content like forms, polls, or appointment pickers
* Provide real-time updates within emails (e.g., cart changes, status updates)
* Improve engagement and reduce redirections to external pages

### Integration with Kasplo

### 1. Via Email API

To send an AMP email via API:

* Use the `content-type: multipart/alternative` in your API request
* Add `text/html`, `text/plain`, and `text/x-amp-html` versions of your content
* Include appropriate headers such as `X-AMP-HTML-Part` for AMP sections

Sample payload:Copy

```

{
  "from": "sender@yourdomain.com",
  "to": "user@example.com",
  "subject": "Welcome to AMP!",
  "html": "Hello (HTML version)",
  "text": "Hello (Plain text version)",
  "amp_html": "...AMP content..."
}
  
```

### 2. Via SMTP

* Ensure the email is sent as `multipart/alternative`
* Include all three parts: plain text, HTML, and AMP HTML
* Your sending domain must be AMP-approved (see below)

Example (raw MIME format):Copy

```

Content-Type: multipart/alternative; boundary="XYZ"

--XYZ
Content-Type: text/plain; charset=UTF-8
Hello (plain text)

--XYZ
Content-Type: text/html; charset=UTF-8
Hello (HTML)

--XYZ
Content-Type: text/x-amp-html; charset=UTF-8


  ...
  ...AMP content...


--XYZ--
```

### Approval Process for Sending AMP Emails

Before sending AMP emails, you must be approved by each ISP you plan to send to. Here’s the general process for each:\
Gmail (Google)

1. Enable DKIM, SPF, and DMARC for your sending domain
2. Use a consistent sending domain and IP with a good reputation
3. Prepare your AMP email samples and ensure they follow [Gmail’s AMP guidelines](https://developers.google.com/gmail/ampemail/)
4. Fill out the [Gmail AMP Registration Form](https://amp.gmail.dev/playground/#compose)
5. Wait for Gmail’s approval (usually 5–7 working days)

### Yahoo Mail

1. Same as Gmail — DKIM, SPF, and DMARC required
2. Reach out to Yahoo with AMP samples via [Yahoo AMP Request Form](https://senders.yahooinc.com/amp/)
3. Approval turnaround time is 5–10 business days

### [Mail.ru](https://mail.ru/)

1. Submit your request to <postmaster@mail.ru>
2. Share sample AMP messages and domains/IPs you’ll use
3. Approval is manual and typically takes 7–10 business days

### Important Guidelines

* AMP content must match the plain HTML version in intent
* You must always include fallback `text/plain` and `text/html` versions
* Use `https` for all AMP components (images, links, JSON endpoints)
* Don’t include external JavaScript — only AMP components are allowed
* Ensure your AMP emails validate using tools like [AMP Playground](https://amp.gmail.dev/playground/)

### Need Help?

Our support team can assist you in:

* Reviewing AMP templates
* Submitting ISP approval forms
* Ensuring your infrastructure (SPF/DKIM/DMARC) is correctly configured

> &#x20;Reach out to us at <support@kasplo.com> to get started with AMP emails.