# Ultimate Email Sending & OTP Verification API Service ## 1. Introduction Welcome to the **Email Sending & OTP Verification API**, a robust, high-availability microservice designed for developers who require immediate, reliable, and secure email delivery and One-Time Password (OTP) generation. Hosted on RapidAPI, this service abstracts the complexities of SMTP servers, MIME types, and secure code generation into four simple, RESTful endpoints. Whether you are building a SaaS platform requiring transactional emails, a mobile application needing user verification (2FA), or a marketing tool sending HTML newsletters, this API provides the infrastructure you need with minimal latency. ### Key Features * **Instant Plain Text Delivery:** Send standard text notifications with zero overhead. * **Rich HTML Support:** Render beautiful, responsive HTML templates for invoices, newsletters, and alerts. * **Secure OTP Generation:** Built-in cryptographic logic to generate unique 6-digit codes. * **Multi-Language Support:** OTP messages are automatically localized in English (`en`), French (`fr`), Malagasy (`mg`), and Spanish (`es`). * **Serverless Architecture:** High scalability handled via RapidAPI's infrastructure. --- ## 2. Authentication & Headers All requests to this API must be authenticated via RapidAPI. You must include the following headers in every HTTP request. | Header | Type | Description | Required | | :--- | :--- | :--- | :--- | | `x-rapidapi-host` | String | `email-sending-or-email-otp-service.p.rapidapi.com` | Yes | | `x-rapidapi-key` | String | Your unique RapidAPI Application Key. | Yes | | `Content-Type` | String | `application/json` | Yes | > **Security Note:** Never expose your `x-rapidapi-key` in client-side code (frontend JavaScript). Always route requests through your backend server. --- ## 3. API Reference ### 3.1. Send Plain Text Email Use this endpoint for system notifications, password resets (where HTML isn't needed), or simple alerts. **Endpoint:** `POST https://email-sending-or-email-otp-service.p.rapidapi.com/send_mail` #### Request Body Schema (JSON) ```json { "email": "recipient@example.com", "texte": "Your message body content goes here." } ``` | Parameter | Type | Required | Description | | :--- | :--- | :--- | :--- | | `email` | String | Yes | The recipient's valid email address. | | `texte` | String | Yes | The plain text body of the email. | #### Response (Success 200) ```json { "message": "Email envoyé avec succès" } ``` --- ### 3.2. Send HTML Email Use this endpoint for branding, newsletters, or rich-text notifications. **Endpoint:** `POST https://email-sending-or-email-otp-service.p.rapidapi.com/send_html` #### Request Body Schema (JSON) ```json { "email": "recipient@example.com", "html": "

Hello!

This is HTML content.

" } ``` | Parameter | Type | Required | Description | | :--- | :--- | :--- | :--- | | `email` | String | Yes | The recipient's valid email address. | | `html` | String | Yes | The raw HTML string. Inline CSS is recommended for maximum client compatibility. | #### Response (Success 200) ```json { "message": "Email HTML envoyé avec succès" } ``` --- ### 3.3. Send OTP (One-Time Password) This endpoint generates a random 6-digit integer, stores it temporarily (stateless logic), and sends it to the user in their preferred language. It returns the code in the response so you can verify it against user input in your database/session. **Endpoint:** `POST https://email-sending-or-email-otp-service.p.rapidapi.com/send_opt` #### Request Body Schema (JSON) ```json { "email": "user@example.com", "language": "en" } ``` | Parameter | Type | Required | Description | | :--- | :--- | :--- | :--- | | `email` | String | Yes | The recipient's email address. | | `language` | String | Yes | The language code for the email body. Options: `fr`, `en`, `mg`, `es`. | #### Response (Success 200) ```json { "message": "OTP envoyé avec succès", "otp": "272189" } ``` **Implementation Tip:** When you receive the response, hash the `otp` value and store it in your database (e.g., Redis) alongside the user's ID with a short expiration time (e.g., 5 minutes). When the user enters the code, hash their input and compare. --- ### 3.4. Get Supported Languages Retrieve the list of languages currently supported for OTP messages. **Endpoint:** `GET https://email-sending-or-email-otp-service.p.rapidapi.com/opt_langue` #### Response (Success 200) ```json { "languages": [ "fr", "en", "mg", "es" ] } ``` --- ## 4. Integration Examples Below are implementation examples for the `/send_html` endpoint. The logic remains similar for other endpoints. ### 4.1. cURL ```bash curl --request POST \ --url https://email-sending-or-email-otp-service.p.rapidapi.com/send_html \ --header 'Content-Type: application/json' \ --header 'x-rapidapi-host: email-sending-or-email-otp-service.p.rapidapi.com' \ --header 'x-rapidapi-key: YOUR_RAPIDAPI_KEY' \ --data '{"email":"recipient@example.com","html":"

Welcome

Thanks for signing up.

"}' ``` ### 4.2. Python (Requests) ```python import requests url = "https://email-sending-or-email-otp-service.p.rapidapi.com/send_html" payload = { "email": "recipient@example.com", "html": "

Welcome

Thank you for joining us.

" } headers = { "Content-Type": "application/json", "x-rapidapi-host": "email-sending-or-email-otp-service.p.rapidapi.com", "x-rapidapi-key": "YOUR_RAPIDAPI_KEY" } response = requests.post(url, json=payload, headers=headers) print(response.json()) ``` ### 4.3. Node.js (Axios) ```javascript const axios = require('axios'); const options = { method: 'POST', url: 'https://email-sending-or-email-otp-service.p.rapidapi.com/send_html', headers: { 'Content-Type': 'application/json', 'x-rapidapi-host': 'email-sending-or-email-otp-service.p.rapidapi.com', 'x-rapidapi-key': 'YOUR_RAPIDAPI_KEY' }, data: { email: 'recipient@example.com', html: '

Welcome

Thank you for joining us.

' } }; try { const response = await axios.request(options); console.log(response.data); } catch (error) { console.error(error); } ``` ### 4.4. PHP (cURL) ```php <?php $curl = curl_init(); curl_setopt_array($curl, [ CURLOPT_URL => "https://email-sending-or-email-otp-service.p.rapidapi.com/send_html", CURLOPT_RETURNTRANSFER => true, CURLOPT_ENCODING => "", CURLOPT_MAXREDIRS => 10, CURLOPT_TIMEOUT => 30, CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1, CURLOPT_CUSTOMREQUEST => "POST", CURLOPT_POSTFIELDS => json_encode([ "email" => "recipient@example.com", "html" => "

Welcome

Thank you for joining us.

" ]), CURLOPT_HTTPHEADER => [ "Content-Type: application/json", "x-rapidapi-host: email-sending-or-email-otp-service.p.rapidapi.com", "x-rapidapi-key: YOUR_RAPIDAPI_KEY" ], ]); $response = curl_exec($curl); $err = curl_error($curl); curl_close($curl); if ($err) { echo "cURL Error #:" . $err; } else { echo $response; } ``` --- ## 5. Troubleshooting & Error Handling While the success messages are straightforward, robust applications should handle potential edge cases. | HTTP Status | Meaning | Possible Cause | Action | | :--- | :--- | :--- | :--- | | **200** | OK | Request processed successfully. | Proceed with your application flow. | | **400** | Bad Request | Invalid JSON body or missing fields (e.g., missing `email`). | Check your JSON syntax and payload keys. | | **401** | Unauthorized | Invalid or missing `x-rapidapi-key`. | Verify your RapidAPI subscription and key. | | **403** | Forbidden | Quota exceeded. | Upgrade your RapidAPI plan. | | **500** | Server Error | Internal processing issue. | Retry the request after a short delay (Exponential Backoff). | --- ## 6. Best Practices for Email Delivery 1. **Rate Limiting:** Although the API scales, ensure your application respects the rate limits of your specific RapidAPI subscription tier to avoid 429 Too Many Requests errors. 2. **HTML Sanitization:** When using `/send_html`, ensure you are not injecting malicious scripts if the content is user-generated. Use inline CSS styles, as many email clients strip `<style>` blocks in the `<head>`. 3. **OTP Security:** The API returns the OTP code in the response body. It is the responsibility of the developer to store this code securely on the server-side to verify the user's subsequent input. Do not send this OTP code to the frontend client directly. 4. **Language Fallback:** Use the `/opt_langue` endpoint to dynamically populate your UI language selector. If a user selects a language not supported (e.g., German), fallback to English (`en`) in your logic before calling `/send_opt`. --- ## 7. Changelog * **v1.0.0:** Initial Release. Support for Text, HTML, and OTP (en, fr, mg, es). For support, please contact us via the RapidAPI dashboard discussion tab. --- **send mail or email send**