← Back to category

Documentation

Sending Email from Your Deployed Site in Clincoo

Sites you deploy on Clincoo can send their own email — order confirmations, contact form notifications, even audience broadcasts. This guide walks you from zero to your first successful request.

Enable the email feature

Open your project on app.clincoo.buzz, go to the Email menu in project settings, then click Aktifkan Email. The feature works per project, so enable it on the project whose deployed site actually needs to send messages.

Get your API key

Open the Kunci API tab on the same page and copy the key formatted clc_email_… Store it as a secret on your deployed site's server side — never hardcoded where the public can read it.

Send email with one request

From your deployed site, send a single POST request to https://app.clincoo.buzz/api/email with a Content-Type application/json header and a body containing the fields action set to send, api_key, to, subject, and html. The reply_to field is optional if replies must land on a different address.

Test first with your own email address in the to field. Once the message arrives, point the same request at your customers or your site's contact form.

Quota and limitations

Each project gets a quota of 1,000 emails per month. The Cloudflare Email Routing backend only delivers to verified addresses, so verify your main recipient address before relying on this channel for important notifications.

Watch the results

The Metrik tab shows delivered and failed statistics, while the Template and Otomasi tabs help you prepare reusable message bodies and automatic sending rules. If an email does not arrive, check the API key and the recipient address before retrying.