4notify Documentation
What you can do with 4notify beyond the panel: an API for your own backend, webhooks, and cross-channel automation.
Getting started
From account to your first API-sent message
Create your account at panel.4notify.net and generate a client_id/client_secret pair from the API credentials page. Use them to request an access token via POST /api/v1/auth/token (OAuth2 client_credentials) — the token is short-lived and your integration simply requests a new one whenever it needs it.
API Reference
Three send endpoints, one pipeline
POST /api/v1/sms, /api/v1/whatsapp and /api/v1/push accept the request with Authorization: Bearer <token> and respond 202 Accepted — the message enters the same queue and runs through the same worker and provider as messages sent from the panel, just tagged internally as "source: api". Every tenant has its own rate limit and quota; going over either returns an explicit error rather than silently dropping messages.
Webhooks & inbound events
Closing the loop on WhatsApp
On WhatsApp we receive delivery events and customer replies back through a webhook verified with your Meta verify token. We don't offer generic third-party connectors (no WooCommerce, Shopify or Zapier plugins) — what we do offer is this webhook plus the send API above, which you wire into your own CRM or backend.
Templates & automated workflows
Reusable content and event-driven triggers
Message templates are defined once per channel and reused from both the panel and the API. Workflows tie a trigger event to a sequence of sends across channels — for example an SMS followed by WhatsApp if the first message isn't read. API credentials carry separate scopes, can be revoked individually from the panel, and show their last-used date.