Questions we
hear often.

A messaging and number verification service: SMS Marketing, WhatsApp Marketing, the OTP API, and Virtual Numbers. Everything runs on one account with one prepaid balance.

SMS Marketing for SMS, RCS, and MMS; WhatsApp Marketing for broadcasts from your own device; the OTP API for verification over SMS or WhatsApp; and Virtual Numbers for receiving codes from other services.

There are no monthly plans. Charges come from recorded usage, such as messages, OTP requests, or virtual number orders.

Create an account, top up your balance, and pick a service. For API integrations, create a token on the API Tokens page and start from the documentation.

It is billed per segment. The composer shows the estimated GSM-7 or Unicode segments before you send. The final count and cost depend on the gateway that processes the message.

When you create a batch through the API, numbers must be unique within a request. That prevents double sends. For file imports, review the recipient summary before starting the batch.

Yes. In the composer, pick a start time instead of sending immediately. The batch waits for its schedule before processing.

Yes. RCS accepts one optional media file; MMS requires one. Media is downloaded and stored before the batch is created.

Yes. Use GET /api/v1/sms for the batch list and GET /api/v1/sms/batches/{id} for message details. Each message has its own status and send attempt count.

One to 1,000 recipients, and numbers must be unique within a request. The API rate limit is 120 requests per minute, counted per token and per account.

No. Connect the device you already use via QR code or pairing code. Once linked, campaigns use that device.

Yes. One dashboard session accepts up to 30 TXT, CSV, or XLSX files, each up to 25 MB. Review the recipient summary before starting the session.

Undelivered messages are marked failed. When the device reconnects, failed messages can be resent from the same session without repeating the whole list.

Yes. A running session can be paused, resumed, or cancelled. Progress and per-message status are preserved.

No. Delivered means the message reached the recipient device. notif. does not report read status as a guarantee.

Random delays, per-batch cooldowns, and gradual slowdowns keep sending within reasonable limits. The values are set at the service level, not per sender.

Yes, after a 60-second cooldown. For the same number and channel, the limit is 5 requests per hour. Reuse the same Idempotency-Key when retrying a request that failed because of a connection issue.

You decide, between 60 and 900 seconds. If omitted, the system uses 300 seconds. The creation response includes expires_at in ISO 8601 format.

The OTP request is marked failed and the code can no longer be verified. The user has to request a new code once the cooldown passes.

They are stored as an HMAC hash with the application key, never as plain text. The original code is only sent to the recipient.

Yes, up to 255 characters, and it must contain {otp} or {code}. If the template is empty, the system uses the default.

Yes. The OTP page in the dashboard has a sandbox tab for testing sends and verification without writing an integration first.

Once the order is ACTIVE. Price and stock are confirmed first, then the number appears in the order details.

The order stays active until it expires. While time remains, resend or reactivation can be tried if the order flags allow it. Otherwise the order ends as EXPIRED.

Yes, when the WhatsApp device integration is active. The order is paired with an available device and the code is sent there.

notif. receives webhooks from virtual number partners. The payload is verified against a secret before processing, so mismatched messages never change an order.

Not yet. Virtual numbers are managed from the dashboard. The public API covers SMS, WhatsApp, and OTP.

No. The catalog depends on partner availability. Combinations without stock show no offer, and no order is created.

Funds are held while a message or OTP request is processed. The hold becomes a charge once the gateway accepts the message. If the gateway rejects it, the hold is released.

If the gateway rejects delivery, the held funds are released. An uncertain status is not treated as success and may go through reconciliation.

Not from the dashboard. The currency is locked when the wallet is created. To move between IDR and USD, contact an admin: the old wallet is closed and a new one is opened.

Yes. The balance page keeps invoices and checkout links. Unfinished invoices can be checked or resumed there.

Whatever gateways are active on your account: Midtrans, Xendit, DOKU, or USDT through NOWPayments. The balance page only lists methods that are already configured.

Send the token in the Authorization header as Bearer notif.<64 hex characters>. Every token has its own permission list, so a token with only sms:read cannot create a batch.

120 requests per minute, counted per token and per account. When you exceed it, the 429 response includes a Retry-After header.

A unique key of up to 255 characters for creating a batch. Reuse the same value when retrying so the batch is not created twice. The same key with a different body is rejected with 409.

The sms.batch.updated and whatsapp.batch.updated events are delivered to a public HTTPS URL on port 443. Every request carries X-Webhook-Id, X-Webhook-Timestamp, and X-Webhook-Signature.

Compute sha256=HMAC(timestamp + "." + raw body, webhook secret) and compare it with X-Webhook-Signature. Use the raw body, not parsed JSON, and reject old timestamps.

At docs.notif.biz/api. It covers endpoints, fields, response examples, limits, and error codes for SMS, WhatsApp, and OTP.