Reach us directly

Email
contact@satz.co.in
Phone
+91 9790060943
Address
Chennai, Tamil Nadu, India

If your question is about the endpoint itself, the API documentation answers most of it — including every response code and a live tester.

Send us a message

Questions

What does it cost?
Nothing. It sends through one mailbox we already pay for, which is exactly why there is a published daily cap per app and why it carries form submissions only — not newsletters, and not transactional mail for your own users.
Do I need a server to use it?
No. The endpoint accepts cross-origin calls from any origin, so your frontend can call it directly with fetch — there is no route of your own to write. The one thing a browser can't do is submit a plain HTML form at it, because the key travels in a request header that a native form submit can't set, so it goes through an AJAX call instead. A key in page JavaScript is readable by anyone, so keep it in an environment variable if you do have somewhere server-side; where you don't, what bounds a scraped key is that it can only deliver to the address that app already confirmed, only in the fields it declares, and only 500 times a day.
How many emails can I send?
500 a day per app, on the UTC day, reset at midnight. Past that, submissions are refused with a 429 rather than dropped silently. It's a limit we can raise — ask us if your form legitimately needs more.
Which email address does the mail come from?
Always ours. The person who filled in your form goes into Reply-To instead, because sending as a stranger's address is spoofing and fails SPF and DMARC checks.
Can I send to an address I don't own?
Only if that address confirms it. We email it an eight-character code, and until the code is entered the app has no working secret key at all.
What happens if a submission has a field I didn't declare?
It is rejected with a 400 and the offending field name, and no email is sent. Add the field to the app in the dashboard and the same request succeeds.