# AnyMatch Email Send API **Send transactional email with one REST call — HTML or plain text, automatic provider failover, and predictable JSON responses.** --- ## Table of contents - [Overview](#overview) - [Why developers choose this API](#why-developers-choose-this-api) - [Common use cases](#common-use-cases) - [Getting started](#getting-started) - [Authentication](#authentication) - [Base URL](#base-url) - [Send email](#send-email) - [Code examples](#code-examples) - [Response reference](#response-reference) - [Rate limits & quotas](#rate-limits--quotas) - [Best practices](#best-practices) - [FAQ](#faq) - [Support](#support) --- ## Overview AnyMatch Email Send API is a production-ready email delivery endpoint built for apps, SaaS products, and automation workflows. Send welcome emails, password resets, receipts, alerts, and notifications without managing SMTP servers or provider SDKs yourself. Submit a recipient, subject, and body — the API handles validation, routing, and delivery through a managed provider pool with automatic failover when a provider is unavailable or over capacity. **Ideal for:** startups, indie hackers, internal tools, MVPs, and teams that want reliable email delivery through a simple HTTP API. --- ## Why developers choose this API - **One endpoint** — `POST /send` covers the full send flow. - **HTML + plain text** — send rich HTML, plain text, or both in the same request. - **Automatic failover** — if the primary mail provider fails, the next available provider is used automatically. - **Structured JSON** — consistent success and error payloads for easy integration. - **Optional overrides** — set `reply_to` and `from_name` per message or rely on sensible defaults. - **Quota transparency** — when limits are reached, responses include usage details and reset timing. --- ## Common use cases | Use case | Example | |----------|---------| | User onboarding | Welcome email after sign-up | | Account security | Password reset and verification codes | | E-commerce | Order confirmations and shipping updates | | SaaS notifications | Billing alerts, usage warnings, admin notices | | Automation | Zapier, n8n, or custom cron jobs triggering sends | --- ## Getting started 1. **Subscribe** to a plan on RapidAPI (free tier available for testing, if offered). 2. **Copy your API key** from the RapidAPI dashboard ([Apps → default-application → Security](https://rapidapi.com/developer/security)). 3. **Send a test request** using the examples below. 4. **Integrate** into your app — most teams are live in under 15 minutes. --- ## Authentication All requests require your RapidAPI subscription key. | Header | Required | Description | |--------|----------|-------------| | `X-RapidAPI-Key` | Yes | Your RapidAPI subscription key | | `X-RapidAPI-Host` | Yes | API host assigned in your RapidAPI listing | | `Content-Type` | Yes | `application/json` for send requests | > Replace `YOUR_RAPIDAPI_KEY` and the host value below with the credentials shown in your RapidAPI app dashboard after subscribing. --- ## Base URL ``` https://anymatch-email.p.rapidapi.com/api/v1 ``` > Update the host in `X-RapidAPI-Host` and the URL above to match your published RapidAPI listing slug. --- ## Send email Deliver a single email to one recipient. ``` POST /send ``` ### Request body | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | `to` | string | **Yes** | Recipient email address | | `subject` | string | **Yes** | Email subject line (max 255 characters) | | `html` | string | Conditional | HTML email body. Required if `text` is omitted | | `text` | string | Conditional | Plain-text body. Required if `html` is omitted | | `reply_to` | string | No | Reply-to address for this message | | `from_name` | string | No | Sender display name (max 255 characters) | At least one of `html` or `text` must be provided. ### Success response — `200 OK` ```json { "status": "sent", "email": { "to": "user@example.com", "subject": "Welcome to Acme", "html": "

Thanks for signing up.

", "reply_to": "support@acme.com", "from_name": "Acme" } } ``` --- ## Code examples ### cURL ```bash curl --request POST \ --url 'https://anymatch-email.p.rapidapi.com/api/v1/send' \ --header 'Content-Type: application/json' \ --header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY' \ --header 'X-RapidAPI-Host: anymatch-email.p.rapidapi.com' \ --data '{ "to": "user@example.com", "subject": "Welcome to Acme", "html": "

Thanks for signing up.

", "text": "Thanks for signing up.", "reply_to": "support@acme.com", "from_name": "Acme" }' ``` ### JavaScript (fetch) ```javascript const response = await fetch('https://anymatch-email.p.rapidapi.com/api/v1/send', { method: 'POST', headers: { 'Content-Type': 'application/json', 'X-RapidAPI-Key': 'YOUR_RAPIDAPI_KEY', 'X-RapidAPI-Host': 'anymatch-email.p.rapidapi.com', }, body: JSON.stringify({ to: 'user@example.com', subject: 'Welcome to Acme', html: '

Thanks for signing up.

', text: 'Thanks for signing up.', reply_to: 'support@acme.com', from_name: 'Acme', }), }); const data = await response.json(); console.log(data); ``` ### Python ```python import http.client import json conn = http.client.HTTPSConnection("anymatch-email.p.rapidapi.com") payload = json.dumps({ "to": "user@example.com", "subject": "Welcome to Acme", "html": "

Thanks for signing up.

", "text": "Thanks for signing up.", "reply_to": "support@acme.com", "from_name": "Acme" }) headers = { "Content-Type": "application/json", "X-RapidAPI-Key": "YOUR_RAPIDAPI_KEY", "X-RapidAPI-Host": "anymatch-email.p.rapidapi.com" } conn.request("POST", "/api/v1/send", payload, headers) res = conn.getresponse() print(res.read().decode("utf-8")) ``` ### PHP ```php <?php $curl = curl_init(); curl_setopt_array($curl, [ CURLOPT_URL => 'https://anymatch-email.p.rapidapi.com/api/v1/send', CURLOPT_RETURNTRANSFER => true, CURLOPT_POST => true, CURLOPT_HTTPHEADER => [ 'Content-Type: application/json', 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY', 'X-RapidAPI-Host: anymatch-email.p.rapidapi.com', ], CURLOPT_POSTFIELDS => json_encode([ 'to' => 'user@example.com', 'subject' => 'Welcome to Acme', 'html' => '

Thanks for signing up.

', 'text' => 'Thanks for signing up.', 'reply_to' => 'support@acme.com', 'from_name' => 'Acme', ]), ]); $response = curl_exec($curl); curl_close($curl); echo $response; ``` --- ## Response reference | HTTP status | `error` value | Meaning | |-------------|---------------|---------| | `200` | — | Email sent successfully | | `401` | `unauthorized` | Missing or invalid API key | | `403` | `forbidden` | API client is disabled | | `422` | — | Validation failed (invalid or missing fields) | | `429` | `quota_exceeded` | Daily or monthly send limit reached | | `429` | — | RapidAPI or per-minute rate limit exceeded | | `503` | `not_delivered` | All providers unavailable or over quota | ### Validation error — `422` ```json { "message": "The html field is required when text is not present.", "errors": { "html": ["The html field is required when text is not present."] } } ``` ### Quota exceeded — `429` ```json { "error": "quota_exceeded", "message": "Monthly send limit reached.", "monthly_limit": 1000, "sent_this_month": 1000, "daily_limit": 50, "sent_today": 12, "resets_at": "2026-06-01T00:00:00+00:00" } ``` ### Delivery failure — `503` ```json { "error": "not_delivered", "message": "Unavailable or over quota." } ``` --- ## Rate limits & quotas Limits apply at two levels: | Limit type | Default behavior | |------------|------------------| | **RapidAPI plan quota** | Defined by your subscribed plan on RapidAPI (requests per month/day) | | **Per-minute throttle** | 60 requests per minute per IP | | **Send quota** | Per-subscriber daily/monthly email caps enforced by the API | When a send quota is exceeded, the API returns `429` with current usage and `resets_at` so you can retry or upgrade your plan. Configure pricing tiers and included send volumes in your RapidAPI **Pricing** tab to align plan limits with API quotas. --- ## Best practices - **Send both `html` and `text`** for better deliverability and client compatibility. - **Use a recognizable `from_name`** so recipients trust the message. - **Set `reply_to`** to a monitored inbox for user replies. - **Handle `429` and `503` gracefully** — queue retries with backoff instead of failing silently. - **Validate emails client-side** before calling the API to avoid unnecessary `422` responses. - **Store message IDs or logs in your app** if you need audit trails beyond API-side logging. --- ## FAQ **Can I send to multiple recipients in one request?** No. Each call sends to a single `to` address. Loop or batch in your application for multiple recipients. **Do I need to configure SMTP myself?** No. Provider routing and failover are handled by the API. **What happens if delivery fails?** The API tries available providers in priority order. If none succeed, you receive `503` with `error: not_delivered`. **Can I use HTML only?** Yes. Provide `html` without `text`, or include both for multipart emails. **Is this suitable for marketing blasts?** This API is designed for **transactional** email (triggered by user actions). High-volume marketing campaigns may require separate infrastructure and compliance review. **Where do I get help?** Contact support@anymatch.tech with your RapidAPI username and a sample request ID or timestamp. --- ## Support - **Email:** [support@anymatch.tech](mailto:support@anymatch.tech) - **Website:** [AnyMatch Technologies](https://anymatch.tech) - **RapidAPI:** Use the **Discussions** tab on this listing for public Q&A We typically respond within 1–2 business days. --- ## Copy-paste snippets for your RapidAPI listing Use these in Studio when creating the listing. ### Short description (Endpoints tab) ``` Send transactional email via REST — HTML or plain text, one endpoint, automatic provider failover, and clear JSON responses. Built for apps, SaaS, and automation. ``` ### Long description (Endpoints tab) ``` AnyMatch Email Send API lets you deliver welcome emails, password resets, receipts, and alerts without running your own mail servers. Features: • Single POST /send endpoint • HTML and plain-text support • Optional reply_to and from_name per message • Automatic provider failover • Transparent quota and error responses Subscribe, grab your RapidAPI key, and send your first email in minutes. ``` ### Suggested categories - Email - Communication - Business - Developer Tools ### Suggested tags `email`, `transactional-email`, `smtp`, `notifications`, `messaging`, `rest-api`