From: Empresa · avisos@empresa.test
To: cliente@example.test
EMPRESA
Payment confirmed
Hi Ana. We received the payment for order KB-2048. Thank you for your trust.
Example transactional email created from a template.
Beta
Transactional email
Transactional email in the same workspace.
Confirm payments, send documents and keep your customers informed by email with fingerprint idempotency, automatic bounce suppression and atomic quotas.
POST /email/send202 ACCEPTED · IDEMPOTENT
{
"domain_id": "UUID_DO_DOMINIO_VERIFICADO",
"from_local": "notificacoes",
"to": "cliente@empresa.ao",
"subject": "Recibo #2048",
"text": "O seu pagamento foi confirmado."
}Atomic monthly volume and daily limit, separate from SMS balance. Accepted does not mean delivered. After an uncertain result, check history before resending; quota is not automatically released.
Explore the workflow
From confirmation to email, without the complexity.
Choose an example, edit the details and see the message preview. In your system, this workflow can also be automated through the API.
Interactive demonstration with fictional data. No email is sent and no balance is used.
Choose template
PreviewFictional data
Preview · placeholder video
See Kamba Email in action.
Authenticate your domain, prepare a template and track your first email.
Kamba Email
Sample- 01Authenticate domain
- 02Prepare template
- 03Send and monitor
Temporary sample footage for reviewing the player. The product video will replace it.
01How to start
From package to first delivery.
Your team uses Kamba Email as another sending product in the same account. No provider account or SMTP configuration is required.
Choose a package
Email volume is purchased separately from SMS credits.
Authenticate your domain
Add the DNS records shown by KambaSMS.
Create or choose a template
Prepare receipts, confirmations and alerts with variables.
Send and monitor
Use the dashboard or API and follow delivery events.
02Domain and environments
Test first. Authenticate once. Send with your brand.
Sandbox explains the request without contacting a real recipient. Production starts only after your company domain is authenticated.
KambaSMS manages the sending provider. Your team only publishes the DNS records shown in the dashboard.
Sandbox
Learn without external delivery
- No verified domain required
- Does not consume production volume
- Returns predictable test states
Production
Send from your own domain
- SPF and DKIM verified
- Active email package
- Real delivery events and suppressions
Add the domain
Choose a domain controlled by your company.
Publish DNS
Copy the SPF and DKIM records exactly.
Wait for verification
KambaSMS confirms when production is ready.
Choose the sender
Use an address such as notifications@yourdomain.
03Email packages
Choose the volume for your operation.
Email volume runs on its own monthly cycle and does not change your SMS and OTP balance.
Piloto
1 000
emails / monthly cycle
5 000 Kz
Essencial
5 000
emails / monthly cycle
15 000 Kz
Negócio
20 000
emails / monthly cycle
45 000 Kz
Escala
50 000
emails / monthly cycle
85 000 Kz
04Transactional use
Messages your customers expect.
Kamba Email is designed for operational communication triggered by an action or relationship with your business.
Receipts and invoices
Order updates
Password recovery
Confirmations and alerts
05API + Dashboard
Simple for the team. Complete for developers.
Send manually, reuse templates or connect your product through the REST API. The same history and volume remain visible in the workspace.
REST API and idempotency
Templates and bulk queues
SPF, DKIM and suppressions
Delivery events and webhooks
06FAQ
Before your first send.
Do I need a Resend account?+
No. KambaSMS manages the sending infrastructure. You use your KambaSMS account and API key.
Does email consume SMS credits?+
No. Kamba Email has its own package and monthly volume.
Do I need to configure SMTP?+
No. You send from the dashboard or REST API. You only need to authenticate a domain through DNS.
Can I use a Gmail or Outlook address?+
No. Production sending requires a domain controlled by your company.
What happens when the volume ends?+
Production sending pauses until another email package is activated. SMS credits remain unchanged.
Can I send promotional campaigns?+
Kamba Email is currently designed for expected transactional messages. Unsolicited promotional sending is not allowed.
Capabilities & Architecture
What is included in Kamba Email.
Active · 01
Authenticated domains (SPF/DKIM) and free Sandbox
Active · 02
SHA-256 payload fingerprint idempotency
Active · 03
Shared suppression guard (direct, bulk and Transactions)
Active · 04
Atomic daily/monthly quota and transactional callbacks
Next step
Test in Sandbox, then move to production.
Use the same KambaSMS workspace, API keys and documentation to integrate without friction.
Before you integrate
Using Kamba Email: what to know.
Check the requirements, usage rules and service boundaries before activating your integration. The documentation contains the full API contracts.
How should I handle request limits?
On HTTP 429, respect the Retry-After header when present. Avoid retry loops. Request limits, balance and OTP quotas are separate controls. A send timeout can have an unknown outcome: inspect the original operation before attempting a new send.
Does the status page guarantee delivery?
The page shows manually reported incidents. No incident report does not prove availability or delivery. For SMS, provider acceptance, DLR-reported delivery and code verification are distinct states; sandbox has no real delivery.
What do I need to get started?
Add a domain you control, configure the displayed DNS records and wait for verification before live use. DNS propagation and provider validation may take time; an SMS Sender ID does not authenticate an email domain.
How does usage work?
Email volume is separate from SMS credits and belongs to a monthly cycle without rollover. Each accepted live recipient uses one unit. A bounce or later failure does not automatically restore it. Sandbox uses no volume.
What are the limits and scope?
Domains, queues and daily limits depend on account access. Do not send unauthorized promotional messages. A verified domain does not guarantee inbox placement; content, reputation and the receiving server also matter.
What should I check if something fails?
Check history and distinguish accepted, delivered, delayed, uncertain, bounced and suppressed. A timeout or uncertain result does not prove rejection: do not retry automatically or assume quota was released. For direct API sends, reuse an Idempotency-Key only with the same content; a 409 conflict requires review, not a new key to force another send. Do not keep retrying suppressed recipients. Opens and clicks are technical signals affected by filters and privacy tools; they do not prove human reading.
Need help? Share the product, time, request ID and a description of the issue. Do not share API keys, OTP codes or personal message content. For account-specific capacity or commitments, confirm the conditions with support.