Joinotify API
Joinotify Cloud is a Meta-approved technology provider that gives you access to the official WhatsApp API (Meta Cloud API) through our infrastructure — with no verified Business Manager, no App Review and nothing to configure inside Meta's dashboards.
Connect a number at app.joinotify.com and you get a
token shaped like sk_live_xxx, ready to use.
Two surfaces, one token
Simplified API — one endpoint per message type, with the payload cut down to what matters. The sender number is resolved from your token.
Mirrored API (/v1) — the Meta Cloud API contract, byte for byte. If you
already have code written against the Graph, swap the domain and the token:
| From | To |
|---|---|
https://graph.facebook.com/v21.0/ | https://api.joinotify.com/v1/ |
Bearer <META_TOKEN> | Bearer sk_live_xxx |
Your Joinotify token fully replaces Meta's token — the real credential is never exposed.
Always send the token in the header
Meta's documentation shows examples with ?access_token= in the URL. That does
not work on Joinotify. The token must always travel in the
Authorization: Bearer sk_live_xxx header.
Rate limits
| Category | Routes | Limit |
|---|---|---|
| Sending messages | POST /messages and POST /v1/.../messages | 500 req/min |
| Media upload | POST /v1/.../media | 60 req/min |
| Everything else | reads and lookups | 60 req/min |
When you go over, the API answers 429 with a Retry-After header telling you how
many seconds to wait.
Blocked endpoints
For safety, the mirror rejects with 403 any path containing subscribed_apps,
register, deregister, request_code, verify_code, assigned_users,
system_users, debug_token, oauth or uploads, as well as a direct POST on a
phone number ID.
Authentication
- HTTP: Bearer Auth
Token generated in the dashboard after connecting a number. Shaped like
sk_live_xxx (or sk_test_xxx). Always send it in the Authorization header —
a token in the query string is not accepted.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |