> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/admin/test-emails.md).

# Test Emails

A single administrative endpoint for sending a **test email** with an arbitrary HTML body, subject and recipient list. It exists to support QA of the email-editor feature: paste the HTML a template produces, choose who receives it, and trigger a real send so the rendered result can be checked in an actual inbox.

This endpoint does **not** use any of the platform's stored email templates. The HTML you send is delivered as-is (with an `html` content type), so it is only a delivery mechanism for content you have already composed elsewhere.

> **Internal use only.** The endpoint requires a staff (admin) token and is intended for internal team/QA use. It is not a general-purpose mail-sending API and must not be exposed to storefront users, since an unrestricted sender would be an open mail-relay / spam vector.

The sender address is the platform's configured no-reply address; only the recipients, subject and body are supplied by the caller.


---

# 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://apidocs.akinon.com/commerce-openapis/admin/test-emails.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.
