Skip to main content
Notifique is the doorman between your code and the customer: it prevents double charges, does not let messages vanish mid-flight, and keeps each workspace isolated from others.

​
What is it?

It’s the set of protections that make every send unique, traceable, and secure. You integrate once; the platform handles what happens after the API accepts the request. Think of a building with a front desk: your code drops off the package at reception; Notifique manages the queue, avoids delivering twice, and records what happened.

​
What does Notifique protect against?

​
Avoid duplicate sends

Connection blipped, timeout fired, and your system retried? In naive integrations, the customer gets charged twice. On Notifique, send a unique identifier in the Idempotency-Key header (we also accept X-Idempotency-Key):
  1. Generate one key per operation (e.g. order ID, payload hash)
  2. Send it in the header on every critical POST
  3. If you repeat the same key within 24 h, the API does not create another message
  4. The response returned is from the first accepted request
Retry as much as you need. The recipient receives once.

​
Nothing gets lost in transit

Server restarts, WhatsApp wobbles, queue briefly unavailable. On fragile systems, the message disappears. Here, each step has a safety net: Like the post office line: one package at a time, in order, with a record if something goes wrong. For final outcomes, combine webhooks (delivery status) with API logs (whether the HTTP request was accepted).

​
Your data and customer data

Recipient reports (Brazilian Law 14.230/2021): Report API (FELCA).

​
What to do on your side

  1. Never commit API Keys. Use .env or a secrets vault
  2. Use Idempotency-Key on critical sends (billing, OTP, confirmation)
  3. Respond 2xx quickly on webhooks and process in the background
  4. Validate HMAC signature on every webhook. See Webhooks
  5. Watch 402 and 403. Often limits or scopes, not code bugs
  6. Test in Sandbox before going to production

​
Next steps