> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/integrations/guides/phoenix.md).

# Phoenix

Learn how to integrate Mailtrap with Phoenix applications to send emails.

This guide shows you how to integrate Mailtrap with Phoenix and send emails using the Email API.

Before we start, you'll need to:

* [Verify your sending domain](https://docs.mailtrap.io/general/sending-domain.md)
* [Create and save an API key](https://docs.mailtrap.io/general/api-tokens.md)

## Send emails using Phoenix and Mailtrap

To integrate Mailtrap and send emails via Phoenix, simply copy/paste the following script into your configuration:

{% code title="Phoenix configuration" %}

```elixir
# config/config.exs
config :sample, Sample.Mailer,
  adapter: Swoosh.Adapters.Mailtrap,
  api_key: "my-api-key"

# lib/sample/mailer.ex
defmodule Sample.Mailer do
  use Swoosh.Mailer, otp_app: :sample
end
```

{% endcode %}

Once you copy the script, make sure to insert your Mailtrap API token instead of the `my-api-key` value.

{% hint style="info" %}
To learn more about API integration, [click here](https://docs.mailtrap.io/email-api-smtp/setup/api-integration.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mailtrap.io/integrations/guides/phoenix.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
