Developers

Tavros Connect WhatsApp API documentation

Send WhatsApp messages from your own software and receive replies and delivery updates on your server. The API is the same as Meta’s WhatsApp Cloud API — if your software already talks to Meta, you change the URL and the key, and that’s it.

Overview

Base URLhttps://tavrosconnect.com/api/v1/  (Meta-style https://tavrosconnect.com/v23.0/ works too)
AuthenticationAuthorization: Bearer tc_live_… (or tc_test_… for test mode)
FormatHTTPS + JSON, UTF-8. Request and response bodies are exactly Meta’s WhatsApp Cloud API.
LanguagesAny language that can make an HTTPS request — PHP, Python, Node.js, Java, C#/.NET, Go, Ruby, VB, Delphi… (TLS 1.2 or newer).
ReceivingWe forward WhatsApp events (customer messages, delivery/read statuses, template updates) to your HTTPS URL, signed with X-Hub-Signature-256.

Everything sent through the API also appears in your Tavros Connect Chats, so your team can see and continue the conversation.

EndpointWhat it doesKey permission
POST /{phone-number-id}/messagesSend any message type; mark a message as readSend messages
POST /{phone-number-id}/mediaUpload an image / document / video / audio → media idMedia
GET /{media-id}, GET /{media-id}/downloadInfo and bytes of media a customer sent youMedia
GET /{waba-id}/message_templatesYour templates and their approval statusTemplates
POST /{waba-id}/message_templatesCreate a template and submit it to MetaManage templates
POST /{template-id}Edit a templateManage templates
DELETE /{waba-id}/message_templates?name=Delete a templateManage templates
POST /contactsSave customer names / tags (shown in Chats)Contacts
GET /messages/{wamid}Delivery status of one message (sent / delivered / read / failed, Meta’s timestamps)Send messages
POST /messages/status:batchThe same for up to 100 wamidsSend messages
GET /messagesSweep the messages you sent, with their status (cursor paging)Send messages
POST /webhooks/replayRe-send stored status events to your webhookSend messages
GET /webhooks/deliveriesEvery webhook attempt we made, with the HTTP code your server returnedSend messages
POST /test/inboundTest keys only: send a fake customer message to your webhookSend messages

Quick start — first message in 5 minutes

  1. Create an account and connect your WhatsApp number (Connect WhatsApp in the menu).
  2. Open Developers / API → Create API key → choose Test. Copy the key (tc_test_…) — it is shown only once. Store it in an environment variable, e.g. TAVROS_API_KEY.
  3. On the same page, copy your Phone number ID (it goes in the URL).
  4. Run the send a template example below. With a test key you get a fake message id and nothing is sent — perfect for building.
  5. When it works, create a Live key (tc_live_…) and use it in production. Nothing else changes.
Why templates? WhatsApp lets businesses start a conversation only with an approved template. Free text is allowed within 24 hours after the customer last wrote to you. Create templates under Templates in Tavros Connect.

API keys & security

Live key tc_live_…Test key tc_test_…
Sends real WhatsApp messagesYesNo — validated, then answered with a fake id
Meta message charges (billed by Meta to your account)Yes (templates)Never
Appears in ChatsYesNo
Webhook eventsReal events from WhatsAppSimulated sent / delivered / read
Rate limitBy your package — see Rate limits60 requests / minute
How many keysBronze 1 · Silver 3 · Gold 10Don’t count toward the package’s keys
  • One secret key, no public key. Every request is made from your server, so a single secret key is enough. Never put a key in a website, a mobile app or a public repository.
  • Permissions: when you create a key, tick only what it needs — Send messages, Media, Templates, Contacts. A billing system that only sends receipts needs just Send messages and Media.
  • IP allowlist: optionally list your server’s public IPs (or ranges like 203.0.113.0/24, IPv6 too). Calls from any other IP get 403 — a stolen key is useless elsewhere. The API usage page shows the IPs that are calling you.
  • Rotation: create a new key, deploy it, then revoke the old one. Revoking takes effect immediately.
  • Keys are stored only as a SHA-256 hash; we can’t show a key again after it is created.

Send a template message

Replace payment_receipt_v1, the language and the variables with one of your approved templates. The number of body parameters must match the {{1}}, {{2}}… in the template.

cURL shown — the same HTTP request works from any language.
curl -X POST 'https://tavrosconnect.com/api/v1/PHONE_NUMBER_ID/messages' \
  -H "Authorization: Bearer $TAVROS_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "messaging_product": "whatsapp",
    "to": "919876543210",
    "type": "template",
    "template": {
      "name": "payment_receipt_v1",
      "language": { "code": "en" },
      "components": [{ "type": "body", "parameters": [
        { "type": "text", "text": "Priya" },
        { "type": "text", "text": "2499" } ] }]
    }
  }'

Response

JSON
{
  "messaging_product": "whatsapp",
  "contacts": [{ "input": "919876543210", "wa_id": "919876543210" }],
  "messages": [{ "id": "wamid.HBgMOTE5ODc2NTQzMjEwFQIAERgSN0Y…", "message_status": "accepted" }]
}

200 means WhatsApp accepted the message. Whether it was delivered and read arrives later as a webhook status with the same id.

Tip — customer names: add the header X-Contact-Name: Rahul%20Patil (URL-encoded) to any send, and Chats shows the name instead of the bare number.

Header media, buttons, currency/date parameters work exactly as in Meta’s template message reference — e.g. a PDF header: {"type":"header","parameters":[{"type":"document","document":{"id":"MEDIA_ID","filename":"Receipt.pdf"}}]}.

Other message types

Every send is the same request as above — POST /{phone-number-id}/messages — only the JSON body changes. Free-form messages (everything except templates) can only be sent within 24 hours of the customer’s last message.

Text

JSON
{ "messaging_product": "whatsapp", "to": "919876543210", "type": "text",
  "text": { "body": "Your order #1042 is ready for pickup 🎉", "preview_url": false } }

Image or document from a public URL

JSON
{ "messaging_product": "whatsapp", "to": "919876543210", "type": "image",
  "image": { "link": "https://example.com/offer.jpg", "caption": "Diwali offer" } }

Document you uploaded (see Upload media)

JSON
{ "messaging_product": "whatsapp", "to": "919876543210", "type": "document",
  "document": { "id": "MEDIA_ID", "filename": "Receipt-1042.pdf", "caption": "Your receipt" } }

Reply buttons (up to 3)

JSON
{ "messaging_product": "whatsapp", "to": "919876543210", "type": "interactive",
  "interactive": {
    "type": "button",
    "body": { "text": "Confirm your appointment on 12 Oct, 5 PM?" },
    "action": { "buttons": [
      { "type": "reply", "reply": { "id": "yes", "title": "Yes, confirm" } },
      { "type": "reply", "reply": { "id": "no",  "title": "Reschedule" } } ] } } }

Location

JSON
{ "messaging_product": "whatsapp", "to": "919876543210", "type": "location",
  "location": { "latitude": 16.705, "longitude": 74.2433, "name": "FitZone Gym", "address": "Rajarampuri, Kolhapur" } }

Mark a received message as read (blue ticks)

JSON
{ "messaging_product": "whatsapp", "status": "read", "message_id": "wamid.HBgM…" }

Upload media

Upload a file once, get a media id, then send it in as many messages as you like (ids stay valid for 30 days). Max sizes: images 5 MB, documents 100 MB, video/audio 16 MB.

cURL shown — the same HTTP request works from any language.
curl -X POST 'https://tavrosconnect.com/api/v1/PHONE_NUMBER_ID/media' \
  -H "Authorization: Bearer $TAVROS_API_KEY" \
  -F messaging_product=whatsapp \
  -F type=application/pdf \
  -F 'file=@Receipt.pdf;type=application/pdf'

# → {"id":"1234567890123456"}  — use it as "document": {"id": "…"} in a send

Media your customers send you arrives in the webhook as an id. GET /{media-id} returns its details with a url on our domain; download it with the same API key (GET /{media-id}/download).

List templates

Returns your templates with their status (APPROVED, PENDING, REJECTED) and components. Filters: name, status, category, language, limit; paging with after.

cURL shown — the same HTTP request works from any language.
curl 'https://tavrosconnect.com/api/v1/WABA_ID/message_templates?status=APPROVED&limit=50' \
  -H "Authorization: Bearer $TAVROS_API_KEY"

Read one template’s status: ?name=order_ready&fields=name,language,status,category,rejected_reason — rejected_reason is filled when Meta rejects it.

Create, edit and delete templates

Needs the key permission Manage templates (tick it under Developers → your key → Edit access). Bodies are Meta’s. With a live key these are real submissions to Meta; with a test key they are only validated and nothing is sent or saved (you get a fake id and status PENDING). Meta’s review result arrives on your webhook as message_template_status_update (APPROVED / REJECTED with a reason), and you can also poll the status with the list call above.

cURL shown — the same HTTP request works from any language.
# Create + submit. Every {{n}} in the BODY needs a sample in example.body_text.
curl -X POST 'https://tavrosconnect.com/api/v1/WABA_ID/message_templates' \
  -H "Authorization: Bearer $TAVROS_API_KEY" -H 'Content-Type: application/json' \
  -d '{ "name": "order_ready", "language": "en", "category": "UTILITY",
        "components": [ { "type": "BODY", "text": "Hi {{1}}, your order {{2}} is ready.",
                          "example": { "body_text": [["Rahul", "A-1042"]] } } ] }'
# → {"id":"1234567890","status":"PENDING","category":"UTILITY"}

# Edit (Meta re-reviews it; status goes back to PENDING)
curl -X POST 'https://tavrosconnect.com/api/v1/TEMPLATE_ID' -H "Authorization: Bearer $TAVROS_API_KEY" -H 'Content-Type: application/json' \
  -d '{ "components": [ { "type": "BODY", "text": "Hello {{1}}, order {{2}} is ready.", "example": { "body_text": [["Rahul", "A-1042"]] } } ] }'
# → {"success":true}

# Delete (all languages of the name; add &hsm_id=TEMPLATE_ID for one language)
curl -X DELETE 'https://tavrosconnect.com/api/v1/WABA_ID/message_templates?name=order_ready' -H "Authorization: Bearer $TAVROS_API_KEY"
# → {"success":true}

Templates with an image, video or document header

A header of format IMAGE, VIDEO or DOCUMENT needs a sample file for Meta’s review. Meta only takes a sample as an upload handle from its own upload API, which is not exposed to API users — so Tavros does that step for you. Two ways:

  • Send a link (simplest). Put a public https:// link to a sample file in example.header_url. Tavros downloads it, uploads it to Meta and submits the template with the resulting handle. Allowed samples: JPEG/PNG up to 5 MB (IMAGE), MP4 up to 16 MB (VIDEO), PDF up to 20 MB (DOCUMENT). The link must be public (no login, no private network address) and on port 443; keep it live until the call returns.
  • Upload the file. POST /{waba-id}/message_template_samples with a multipart field file returns {"h": "…"}; pass it as example.header_handle.
cURL shown — the same HTTP request works from any language.
# 1) Link: Tavros fetches the sample for you
curl -X POST 'https://tavrosconnect.com/api/v1/WABA_ID/message_templates' \
  -H "Authorization: Bearer $TAVROS_API_KEY" -H 'Content-Type: application/json' \
  -d '{ "name": "membership_invoice_pdf", "language": "en", "category": "UTILITY",
        "components": [
          { "type": "HEADER", "format": "DOCUMENT",
            "example": { "header_url": ["https://example.com/sample-invoice.pdf"] } },
          { "type": "BODY", "text": "Hi {{1}}, your invoice {{2}} is attached.",
            "example": { "body_text": [["Priya", "INV-0001"]] } } ] }'
# → {"id":"1234567890","status":"PENDING","category":"UTILITY"}

# 2) Upload: get a handle, then use it as example.header_handle
curl -X POST 'https://tavrosconnect.com/api/v1/WABA_ID/message_template_samples' \
  -H "Authorization: Bearer $TAVROS_API_KEY" -F file=@sample-invoice.pdf
# → {"h":"4::aW1hZ2U6..."}

# Sending it later: the header parameter goes in the message, as on Meta's Cloud API
curl -X POST 'https://tavrosconnect.com/api/v1/PHONE_NUMBER_ID/messages' \
  -H "Authorization: Bearer $TAVROS_API_KEY" -H 'Content-Type: application/json' \
  -d '{ "messaging_product": "whatsapp", "to": "919876543210", "type": "template",
        "template": { "name": "membership_invoice_pdf", "language": { "code": "en" },
          "components": [
            { "type": "header", "parameters": [ { "type": "document",
                "document": { "link": "https://example.com/invoice-0001.pdf", "filename": "Invoice.pdf" } } ] },
            { "type": "body", "parameters": [ { "type": "text", "text": "Priya" }, { "type": "text", "text": "INV-0001" } ] } ] } }'

Errors come back in Meta’s format, e.g. (#100) Invalid parameter: a DOCUMENT header needs a sample or … a DOCUMENT header sample must be application/pdf, but the link gave text/html. Test keys download and check the sample the same way but upload nothing to Meta. Editing a media-header template (POST /{template-id}) accepts header_url too. The PHONE_NUMBER_ID is the id of your number as listed in Tavros Connect (the same id /messages and /media use), not the phone number itself.

Meta rules apply: lowercase names with underscores, a deleted name can’t be re-used for 30 days, and an approved template can be edited only about once a day (10 times a month).

Save contacts

A Tavros Connect extension (not in Meta’s API): send your customers’ names and tags so Chats and campaigns show names. Up to 1,000 per call; existing numbers are updated, never duplicated. Numbers without a country code are treated as Indian (+91).

cURL shown — the same HTTP request works from any language.
curl -X POST 'https://tavrosconnect.com/api/v1/contacts' \
  -H "Authorization: Bearer $TAVROS_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{ "contacts": [
        { "phone": "919876543210", "name": "Rahul Patil", "tags": ["members"] },
        { "phone": "9123456789", "name": "Sneha Joshi" } ] }'

# → {"success":true,"created":1,"updated":1,"invalid":0,"over_limit":0,"contacts":[…]}

Webhooks — receive messages and statuses

  1. Build an HTTPS endpoint on your server (examples below).
  2. In Tavros Connect → Developers / API → Webhook, enter its URL, a verify token (any string you choose) and a signing secret. Press Verify and save — we call your URL with GET ?hub.mode=subscribe&hub.verify_token=…&hub.challenge=123 and your endpoint must answer with the challenge.
  3. From then on we POST every event to your URL, signed: X-Hub-Signature-256: sha256=HMAC_SHA256(raw body, signing secret). Always check it.
  4. Answer 200 within 10 seconds (do heavy work afterwards). Failed deliveries are retried 9 times over about 34 hours (1 min, 5 min, 15 min, 1 h, 3 h, 6 h, 12 h, 12 h) and listed under Recent webhook deliveries — and, with every attempt and your HTTP code, in GET /webhooks/deliveries.
Moving from Meta’s Cloud API? Use your Meta app secret as the signing secret and your existing receiver works unchanged — the bodies are Meta’s own format.
EventWhere in the body
Customer sent a message (text, image, button reply, location…)entry[].changes[].value.messages[] (+ contacts[] with their profile name)
Your message was sent / delivered / read / failedentry[].changes[].value.statuses[] — id is the wamid you got when sending
Template approved / rejectedchanges[].field = "message_template_status_update"
cURL shown — the same HTTP request works from any language.
# What we send to your URL (a customer wrote "Hi"):
POST /whatsapp/webhook HTTP/1.1
Content-Type: application/json
X-Hub-Signature-256: sha256=5f8a3c…   ← HMAC-SHA256 of the raw body with your signing secret

{
  "object": "whatsapp_business_account",
  "entry": [{
    "id": "WABA_ID",
    "changes": [{
      "field": "messages",
      "value": {
        "messaging_product": "whatsapp",
        "metadata": { "display_phone_number": "912312950811", "phone_number_id": "PHONE_NUMBER_ID" },
        "contacts": [{ "profile": { "name": "Rahul" }, "wa_id": "919876543210" }],
        "messages": [{ "from": "919876543210", "id": "wamid.HBgM…", "timestamp": "1760000000",
                       "type": "text", "text": { "body": "Hi" } }]
      }
    }]
  }]
}

A status event looks like {"statuses":[{"id":"wamid…","status":"delivered","timestamp":"…","recipient_id":"919876543210","pricing":{"billable":true,"category":"utility"}}]}. A failed status carries errors[] with Meta’s error code (see Errors).

Delivery status & webhook replay

Every message you send gets a wamid. Its life is accepted (we took your request) → sent (one grey tick) → delivered (two grey ticks) → read (two blue ticks), or failed. You get each step as a webhook status — and you can also pull it at any time, e.g. to reconcile messages whose webhook your server missed. All five calls need the key permission Send messages and only see messages sent with that key.

Where the data comes from. Meta’s Cloud API has no endpoint to read a message’s status, so these calls return the status events Meta sent us, stored unchanged. sent_at, delivered_at, read_at and failed_at are Meta’s own statuses[].timestamp (UTC) — never the time we received the event (that is received_at). ?refresh=true is accepted and adds a refresh block saying exactly this; it does not (cannot) ask Meta. We keep message and status data for at least 90 days (unless you chose a shorter period in settings) and the webhook delivery log for 30 days.
\

GET /messages/{wamid}

cURL shown — the same HTTP request works from any language.
curl "https://tavrosconnect.com/api/v1/messages/wamid.HBgMOTE5ODc2NTQzMjEwFQIAERgSM0E4" \
  -H "Authorization: Bearer tc_live_YOUR_KEY"
JSON
{
  "wamid": "wamid.HBgMOTE5ODc2NTQzMjEwFQIAERgSM0E4",
  "phone_number_id": "PHONE_NUMBER_ID",
  "to": "919876543210",
  "type": "template",
  "template": "payment_receipt_v1",
  "status": "delivered",                       // highest state reached: accepted | sent | delivered | read | failed
  "timestamps": {
    "accepted_at":  "2026-11-15T08:34:18Z",    // when we accepted your API request
    "sent_at":      "2026-11-15T08:34:19Z",    // Meta status=sent timestamp
    "delivered_at": "2026-11-15T08:34:21Z",    // Meta status=delivered timestamp
    "read_at":      null,
    "failed_at":    null
  },
  "error": null,                               // failed: {"code":131026,"title":"Message undeliverable","message":"…","details":"…"}
  "events": [                                  // raw history, ordered by Meta timestamp; out-of-order events are kept
    {"status": "sent",      "timestamp": "2026-11-15T08:34:19Z", "received_at": "2026-11-15T08:34:20Z"},
    {"status": "delivered", "timestamp": "2026-11-15T08:34:21Z", "received_at": "2026-11-15T08:34:21Z",
     "conversation": {"id": "…", "origin": {"type": "utility"}}, "pricing": {"billable": true, "category": "utility"}}
  ]
}

404 if the wamid is unknown, was sent with another key, or is past retention. Status rules: status is the furthest of sent → delivered → read that Meta reported; it is failed only if Meta reported failed and never delivered/read. If read arrives before delivered, both are shown as received — nothing is inferred or dropped. Test-key messages (wamid.TEST_…) are not stored.

\

POST /messages/status:batch

cURL shown — the same HTTP request works from any language.
curl -X POST "https://tavrosconnect.com/api/v1/messages/status:batch" \
  -H "Authorization: Bearer tc_live_YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"wamids":["wamid.HBgMOTE5ODc2NTQzMjEwFQIAERgSM0E4","wamid.HBgMOTE5ODc2NTQzMjEwFQIAERgSM0E5"]}'
JSON
{"data": [ { …same object as above… }, … ],
 "not_found": ["wamid.HBgMOTE5ODc2NTQzMjEwFQIAERgSM0E5"]}

1 to 100 wamids per request. Counts as one read call (see Rate limits; every package allows at least 60 read calls a minute).

\

GET /messages — sweep everything from the last N hours

cURL shown — the same HTTP request works from any language.
curl "https://tavrosconnect.com/api/v1/messages?since=2026-11-15T00:00:00Z&status=failed&limit=100" \
  -H "Authorization: Bearer tc_live_YOUR_KEY"\
# next page:  …&cursor=NEXT_CURSOR_FROM_PREVIOUS_RESPONSE
Query
since, untilISO 8601 (2026-11-15T09:30:00Z); filter on the time we accepted the message. No zone = UTC.
statusaccepted, sent, delivered, read or failed (the message’s current status)
toOne recipient, country code + number
limit1–200, default 100
cursor, orderPass next_cursor back to continue; order=asc (default, oldest first — best for sweeps) or desc
JSON
{"data": [ { …message object… }, … ], "next_cursor": "bTQyMA", "has_more": true}

A page can hold fewer than limit items when you filter by status; keep following next_cursor until has_more is false.

\

POST /webhooks/replay — recover from downtime

Re-sends the stored status events to your configured webhook URL, signed with the same X-Hub-Signature-256. Each event is its own delivery, in Meta’s exact format (statuses[] holds exactly one object, timestamp / errors / conversation / pricing unchanged), oldest first. Your receiver should dedupe on wamid + status.

cURL shown — the same HTTP request works from any language.
# by message
curl -X POST "https://tavrosconnect.com/api/v1/webhooks/replay" -H "Authorization: Bearer tc_live_YOUR_KEY" \
  -H "Content-Type: application/json" -d '{"wamids":["wamid.HBgMOTE5ODc2NTQzMjEwFQIAERgSM0E4"]}'

# by time window: events we RECEIVED between these times (your downtime)
curl -X POST "https://tavrosconnect.com/api/v1/webhooks/replay" -H "Authorization: Bearer tc_live_YOUR_KEY" \
  -H "Content-Type: application/json" -d '{"since":"2026-11-15T09:00:00Z","until":"2026-11-15T11:00:00Z"}'
JSON
{"queued": 3, "skipped": 0, "matched": 1, "not_found": [], "note": "…"}   // HTTP 202

Up to 500 wamids, or at most 1000 events per call (narrow the window if you get an error); 5 requests per minute. Delivery is asynchronous — follow it with GET /webhooks/deliveries?replay=true. Your webhook must be set and turned on.

\

GET /webhooks/deliveries — what we sent you and what you answered

cURL shown — the same HTTP request works from any language.
curl "https://tavrosconnect.com/api/v1/webhooks/deliveries?since=2026-11-15T00:00:00Z&status=failed" \
  -H "Authorization: Bearer tc_live_YOUR_KEY"
JSON
{"data": [{
    "id": 4812, "created_at": "2026-11-15T08:34:20Z",
    "status": "delivered",                    // pending (will retry) | delivered | failed (gave up)
    "replay": false, "attempts": 2, "last_http_status": 200, "last_error": null,
    "delivered_at": "2026-11-15T08:35:21Z", "next_attempt_at": null,
    "events": [{"field": "messages", "wamid": "wamid.…", "status": "delivered", "timestamp": "1794731541"}],
    "attempt_log": [
      {"attempt": 1, "at": "2026-11-15T08:34:20Z", "http_status": 503, "error": "HTTP 503", "ms": 214},
      {"attempt": 2, "at": "2026-11-15T08:35:21Z", "http_status": 200, "error": null,       "ms": 96}
    ]}],
 "next_cursor": null, "has_more": false}

Newest first. Filters: since, until, status (pending, delivered, failed), replay (true/false), wamid, include_payload=true, limit (1–100), cursor. http_status is null when we could not reach your server (DNS, timeout, TLS). Kept 30 days.

Webhook format guarantees. Statuses are forwarded as Meta sent them: sent, delivered, read and failed each as its own event (one status per changes[] entry, never merged), with Meta’s timestamp (epoch seconds, as a string), errors[], conversation and pricing untouched. We never reorder or drop events — a read may reach you before its delivered; use the timestamps. Non-2xx answers are retried as described in Webhooks.

\

Test mode

Create a Test key (tc_test_…) and build your whole integration without sending a single real message. The URLs, bodies and responses are the same as live.

  • Sends are validated, not sent. We check the phone number id belongs to you, the to number, the message body, and for templates: the name, the language, that it is approved and that the number of body parameters matches. Errors are the same codes as live (e.g. 132001, 132000).
  • A valid send answers 200 with a fake id wamid.TEST_… and then pushes sent → delivered → read statuses to your webhook.
  • Magic numbers: any to ending in 0000 (e.g. 919800000000) gets a failed status with error 131026 — use it to test your failure handling.
  • Media uploads return a fake id (nothing stored). Contacts are a dry run: the answer says what would be created or updated, with "test": true, and nothing is saved.
  • Template list and media downloads return real data — they only read.
  • Nothing is sent to Meta, no Active Day is used, nothing appears in Chats, and test calls are marked test in your API log and usage reports. Responses carry the header X-Tavros-Mode: test.

Simulate a customer writing to you

cURL shown — the same HTTP request works from any language.
curl -X POST 'https://tavrosconnect.com/api/v1/test/inbound' \
  -H "Authorization: Bearer $TAVROS_TEST_KEY" \
  -H 'Content-Type: application/json' \
  -d '{ "from": "919876543210", "name": "Rahul", "text": "Hi, is my membership active?" }'

# → {"success":true,"delivery_id":123}   — your webhook received a real-looking "messages" event

Optional field phone_number_id picks which of your numbers it is sent to (default: the first).

Rate limits

Limits are per business (all its live keys together) and depend on its package (the free trial has Silver’s):

LimitBronzeSilverGold
Send speed (POST …/messages; bursts of up to 10)2 msg/sec10 msg/sec40 msg/sec
Unique recipients per day (resets at midnight India time; a repeat recipient counts once)1,00010,000No cap from us
Read calls (mark as read, templates, media, contacts) per minute603001,000
Live API keys1310

Test keys: 60 requests per minute, no daily cap. Need more for large campaigns? Write to us — we can raise it per business. Every response tells you where you stand:

JSON
X-RateLimit-Limit: 10          ← messages/sec (sends) or calls/min (reads)
X-RateLimit-Remaining: 7
X-RateLimit-Reset: 1           ← seconds until the limit is fully available again

Over a limit you get 429 with error code 4, a Retry-After header and error.type saying which limit:

  • rate_limited — send speed or read calls. Wait Retry-After seconds and retry (our PHP SDK does this for you).
  • daily_api_quota_exceeded — today’s unique recipients are used. Messages to people you already messaged today still go through; new recipients wait until midnight India time (Retry-After) or a bigger package. Don’t retry in a loop.
cURL shown — the same HTTP request works from any language.
HTTP/1.1 429 Too Many Requests
Retry-After: 1
{"error":{"message":"(#4) Bronze allows 2 messages/sec. Retry after 1s or upgrade to Silver.","type":"rate_limited","code":4,"fbtrace_id":"TC…"}}

HTTP/1.1 429 Too Many Requests
Retry-After: 30240
{"error":{"message":"(#4) Bronze allows 1,000 unique recipients a day through the API, and today’s are used (1,000). …","type":"daily_api_quota_exceeded","code":4,"fbtrace_id":"TC…"}}

WhatsApp has its own limits on top of ours: a new number can message 250 unique customers per 24 h (rising to 1K, 10K, 100K with good quality), and about 80 messages per second per number. Those errors come back as Meta codes 131056, 130429 or 80007.

Errors

Errors always have Meta’s shape, so existing error handling keeps working:

JSON
{ "error": { "message": "(#132001) Template name does not exist in the translation", "type": "OAuthException", "code": 132001, "fbtrace_id": "TC9F2A…" } }

From Tavros Connect

HTTPcodeMeaningWhat to do
401190API key missing, wrong or revokedSend Authorization: Bearer tc_live_…; create a new key if it was revoked
40310The key lacks the permission, or the request came from an IP not in its allowlistEdit the key under Developers (permissions / IPs)
403200Your plan doesn’t include the API, or the subscription expiredRenew or upgrade under Billing
400131042Meta couldn’t charge your WhatsApp account (payment method / eligibility)Add or update a payment method in WhatsApp Manager (Meta)
403200No Active Days left (sending paused)Recharge Active Days under Billing
4294rate_limited: your package’s send speed or read calls per minute (or too many invalid keys from your IP)Wait Retry-After seconds and retry
4294daily_api_quota_exceeded: today’s unique API recipients are usedWait until midnight India time or move to a bigger package; repeat recipients still work
400100Bad request — unknown phone number id, missing field, wrong formatRead the message; check the phone number id on the Developers page
5002Temporary problem at Tavros Connect or MetaRetry after a few seconds

Common WhatsApp (Meta) errors — passed through unchanged

codeMeaningWhat to do
131047More than 24 hours since the customer’s last messageSend a template instead of free text
132001Template doesn’t exist in that language (or not approved)Check the name + language code on the Templates page
132000Wrong number of template parametersSend one parameter per {{n}}
132012A parameter has the wrong format (e.g. empty text, new lines)Remove line breaks / tabs; no empty values
131026Message undeliverable (not on WhatsApp, old app, blocked you)Use another channel for this customer
131049Meta held back a marketing message to protect engagementDon’t retry immediately; send fewer marketing messages to this user
131050The customer stopped marketing messages from youMark them opted-out
131056Too many messages to the same customer in a short timeSlow down for that number
130429Throughput limit (messages per second) reachedRetry with back-off
131053Media upload error (unsupported / too big)Check type and size (images: JPEG/PNG ≤ 5 MB)
131031Your WhatsApp account is locked or restrictedCheck WhatsApp Manager / contact us
368Temporarily blocked for policy violationsReview quality and template content

Migrating to Tavros Connect

From Meta’s WhatsApp Cloud API — 3 changes

  1. Replace https://graph.facebook.com with https://tavrosconnect.com. Paths stay the same (/v23.0/{phone-number-id}/messages).
  2. Replace Meta’s access token with a Tavros Connect API key.
  3. Enter your webhook URL in Tavros Connect instead of the Meta app (use your Meta app secret as the signing secret to keep your signature check).

From WATI, Interakt, AiSensy or another provider

Your WhatsApp Business Account, number and approved templates belong to you — connect the same account to Tavros Connect and they come along. Then point your code at one endpoint:

You call todayCall instead
WATI sendTemplateMessage (template_name, parameters[{name,value}])POST /api/v1/{phone-number-id}/messages with "type":"template" — put the values, in order, in components[0].parameters (example)
Interakt /v1/public/message/ (type: "Template", bodyValues)
AiSensy campaign API (campaignName, destination, templateParams)
Session / free-text message endpointsSame endpoint with "type":"text"
Provider-specific webhook formatMeta’s standard format (above) — signed with X-Hub-Signature-256
Contact / attribute APIsPOST /api/v1/contacts

Phone numbers are always country code + number without + (e.g. 919876543210). Need a hand? Our team helps you migrate for free — book a call.

SDK, OpenAPI & Postman

Questions or something missing? Email tavrosconnect@gmail.com.

Related resources

Get your API key and send your first message today

Create your free account, connect your number and send your first message in minutes.

Create free account