What C-Connect is
The platform, the panel and the API, in two pages.
C-Connect delivers your application's transactional email: receipts, verification codes, password recoveries, order confirmations. Everything somebody is expecting to receive because they did something.
What it does for you
Delivering email is not the same as sending it. The difference is what happens next: who received it, who bounced, who marked it as spam, and what has to change so the next message lands in the inbox rather than in the junk folder.
C-Connect takes care of that part:
- Authenticating your domain. SPF, DKIM and DMARC, with the records you have to publish written exactly as they should end up.
- Reputation kept apart per stream. A marketing campaign does not affect the delivery of your receipts.
- Suppressions. An address that bounced for good stops being contacted, without you having to keep that list on your side.
- Events. Every acceptance, deferral, bounce and complaint is recorded and can be pushed to your system.
How you talk to us
There are three ways in, and they all end up in the same place.
| Way in | What for |
|---|---|
| HTTP API | An application of yours that sends from code. |
| SMTP submission | A system that only knows how to send over SMTP. |
| Panel | Seeing what happened, configuring domains and keys. |
The API and SMTP accept the same message and produce the same result: the same DKIM signature, the same Return-Path, the same events.
What you need before you start
- A sending domain, preferably a dedicated subdomain, something like
mail.mycompany.com. - Access to the DNS zone of that domain.
- An API key, which you create in the panel.
The next page walks you through those three steps up to your first delivered message.