HELP & Documents


Date: 2016.7.22        Author: SysAdmin

Search index: (title and article description search)

No record was found!



An easy way to send emails from your WEB page using JQuery, Angular, React, NodeJS or from any application that can send HTTP requests.

API for email sending. Use with WEB applications or automated messages within your application.

RESTful web service:

Method: POST


Authorization: one of two

- JWT (header)

- APIKEY (body request)

Request Body: (as JSON object)


  • from - The e-mail address of the sender.  (required)
    object {"name":"from name","address":"from@address.ext"}
  • sender - An e-mail address that will appear on the Sender:
    object {"name":"sender name","address":"sender@address.ext"}
  • to - An array of recipients e-mail addresses that will appear on the To: (required)
    object {"name":"to name","address":"to@address.ext"} or string "to@address.ext"
  • replyTo - An e-mail address that will appear on the Reply-To: (required)
    string "replyto@address.ext"
  • subject - The subject of the e-mail (required)
  • text - The plaintext version of the message as an Unicode string, Buffer, Stream or an object {path: '...'}
  • html - The HTML version of the message as an Unicode string, Buffer, Stream or an object {path: '...'} (required TEXT or HTML)
  • attachments - An array of attachment objects
        [ { // encoded string as an attachment 
            'filename': 'text1.txt',
            'content': 'aGVsbG8gd29ybGQh',
            'encoding': 'base64'

      [ {   // use URL as an attachment 
            filename: 'license.txt',
            path: ''
        The entire request body size should not exceed 5Mb including attached files. If larger files should be added please use the URL attachment form like previous.

        Please check FILE API for files uploads.

  • messageId - Optional Message-Id value, random value will be generated if not set
  • date - Optional Date value, current UTC string will be used if not set
  • encoding - Optional transfer encoding for the textual parts
  • textEncoding - Sets explicitly which encoding to use for text parts (quoted-printable or base64). If not set then encoding is detected from text content (mostly ascii means quoted-printable, otherwise base64)

Response: (as JSON object)

Done: status code 200


Error: status code 401

{"error":true,"err:":<error object>}

Sample body command:

"sender":{"name":"Popescu Ion","address":"<>"},
"subject":"Test email - MSAS", "html":"<p>Hello world</p>",


{"from":"","to":"<>","replyTo":"","sender":{"name":"AP","address":""},"subject":"Test email - MSAS","html":"<p>Hello world !!</p>","apikey":"A84UIIIHUHIH"}

From address domain name should be one of the platform public domain names, same set within your APIKEY, the address is verified against spam with the DNS SPF TXT record  by the receiver server, it should folow anti spam policies to protect the sending service to be black listed.

Gmail, Yahoo and a lot of others mail servers will check the SPF record and eventually block your email or at least put into SPAM if the SPF record does not match.

Allowed domain names: , , ,

sample RESTClient command and response

Loading data

Loading WordBricks ...

| 1.1.1. Welcome| 1.1.2. Register a new account| 1.1.3. Start| 1.1.4. Technical support| 1.2.1. New website| 1.2.2. New page| 1.2.3. Sections / Page BLOCKS| 1.2.4. Settings| 1.2.5. Save / Backup / Restore| 1.2.6. Background| 1.2.7. My pages| 1.2.8. Page settings| 1.2.9. Website header| 1.2.10. Website menu| 1.2.11. Publish| 1.2.12. Compatibility| 1.2.13. Specials blocks| 1.2.14. DATABLOCKS| 1.2.15. Contacts Form| 1.2.16. Numbers Shuffle - Game| 1.2.17. ChatBox| 2.1.1. WEB hosting| 2.2.1. Hosting plans| 2.3.1. Domain Names| 2.3.2. Register a new domain name| 2.3.3. Domain name management| 2.3.4. Add a SSL certificate| 2.3.5. Create a SSL certificate| 2.3.6. Domain Name Redirects| 2.4.1. SEO informations| 3.1.1. DRIVE| 3.2.1. Files storage| 3.2.2. API drive access| 3.2.3. Safe share files| 3.3.1. WebDO IDE| 4.1.1. Email| 4.1.2. Email Services Names| 5.1.1. Databases| 5.1.2. API key| 5.2.1. Micro data| 5.3.1. Datasets (test fake data)| 6.1.1. We use SOA| 6.2.1. Authorization| 6.2.2. File access| 6.2.3. SendMail| 6.2.4. QR Code| 6.2.5. Document storage API| 6.2.6. MicroData API| 6.2.7. SQL API| 6.2.8. IP API| 6.2.9. DRIVE API| 6.2.10. Link Redirects API| 7.1.2. WebDo CLOUD| 7.1.3. Services Domains| 8.1.1. Payment| 8.1.2. European VAT| 8.2.1. Privacy policies| 8.2.2. Refund policies| 8.2.3. Change web hosting plan| 8.2.4. Minimum order value| 9.1.1. Terms and conditions| 10.1.2. About us| 10.1.2. | 11.1.3. Newsletter Application| 11.2.1. Dashboard| 11.2.2. Subscribers| 11.2.3. Campains| 11.2.4. Email Builder| 11.2.5. Forms| 11.2.6. Forms Builder| 11.2.7. Subscribers Management| 11.2.8. Integrate a custom subscription form using webdo website builder| 12.1.1. Survey Application| 12.2.1. Dashboard| 12.2.2. Add/Edit survey| 12.2.3. Settings| 12.2.4. Campaigns| 12.2.5. Reports| 12.2.6. Survey preview| 12.2.7. Page jumps| 12.2.8. Question types| 13.1.1. E-Detailing Application| 13.2.1. Dashboard| 13.2.2. Presentations| 13.2.3. Campaigns| 13.2.4. Reports| 13.2.5. Templates|