New
Developers

Build messaging into your own product

Build WhatsApp into your own product — campaigns, templates, chatbots, media and webhooks over a clean REST API.

  • Base URL https://api.nuke.co.in/api/v1/developer
POST /whatsapp/campaign
# Send an approved template to your customers
curl -X POST "https://api.nuke.co.in/api/v1/developer/whatsapp/campaign" \
  -H "Authorization: Bearer cfs_your_token" \
  -H "Content-Type: application/json" \
  -d '{
    "template_name": "diwali_offer",
    "numbers": ["919876543210", "919812345678"],
    "attribute1": "Rahul"
  }'
200 { "success": true, "data": { "request_id": "WCAMP_…", "status": "queued" } }
What you can build

One API for the whole platform

Everything your team does in the panel can be automated from your own systems.

Campaigns & session messages

Send templates to one or thousands of numbers with JSON or a CSV upload, and reply inside the 24-hour window.

Templates

Create templates — including carousels, Flows and OTP — and check their approval status.

Chatbots & automations

Create, edit, switch on and delete chatbots and keyword automations using the same JSON as the visual builder.

Webhooks

Receive incoming messages, delivery statuses and copies of bot replies on your own URL, signed with your secret key.

Media

Upload files for replies and download the images, videos, voice notes and documents customers send you.

Tokens for every account

A master token acts for you and every account under you; account tokens are locked to one client.

Your app and Indew, talking both ways

Call the API to send; receive everything that happens next on your webhook.

  1. Your appCRM, website, ERP or your own panel
  2. Developer APIPOST /whatsapp/campaign with your token
  3. WhatsAppDelivered to your customer
  4. Your webhookReplies, statuses and bot replies arrive back
Endpoints

The API at a glance

All paths are relative to the base URL. Send your token as Authorization: Bearer … or x-api-key.

Tokens & accounts

POST/tokensCreate a master token (panel login)
GET/tokensList your tokens — prefix and last use only
DELETE/tokens/{id}Revoke a token
POST/accounts/tokensIssue an account token for one client
GET/accounts/tokensList the account tokens you issued

Messaging

POST/whatsapp/campaignSend a template campaign — JSON or a CSV upload
POST/whatsapp/sessionSend a message inside the 24-hour window
POST/whatsapp/subscribeForward a number’s events to your webhook

Templates & account

POST/whatsapp/templateCreate a template and submit it to Meta
GET/whatsapp/template/statusCheck a template’s approval status
GET/whatsapp/phone-numbersYour number, quality rating and throughput
GET/whatsapp/business-profileRead the business profile
PUT/whatsapp/business-profileUpdate the business profile

Chatbots & automations

GET/whatsapp/chatbotsList chatbots
POST/whatsapp/chatbotsCreate a chatbot — flow JSON and keywords in one call
PUT/whatsapp/chatbots/{id}Rename, switch on or off, or replace the flow
GET/whatsapp/chatbots/check-nameCheck that a chatbot name is free
POST/whatsapp/automationsCreate a keyword automation
PUT/whatsapp/automations/{id}Change keywords, matching or status
DELETE/whatsapp/automations/{id}Delete an automation
GET/whatsapp/automation-textsSaved text replies — also POST, PUT, DELETE

Media & files

POST/whatsapp/filesUpload a file to reply with
GET/whatsapp/filesList the account’s files
GET/whatsapp/media/{media_id}Download media a customer sent you
Tokens

Two kinds of token, one simple rule

Pick the one that matches how your system is built.

Master token

Belongs to your main account. Acts for you and every client or reseller under you — pass the account’s username on each call. Campaign credits are charged to your main account.

Account token

Issued by your master token for one client. Locked to that account, so no username is needed — ideal when each client is configured separately in your panel.

Webhooks

Everything that happens, on your URL

Subscribe a number once. Every event arrives in Meta’s webhook format, signed with your secret key in the X-Secret-Key header.

messages

Incoming messages — text, button taps, images, voice notes, documents and locations.

statuses

Sent, delivered, read and failed updates for every message you send.

message_echoes

Copies of replies sent by chatbots and automations, so your inbox stays complete.

Getting started

From token to first message in four steps

  1. 01

    Create a token

    Generate a developer token from your panel login.

  2. 02

    Subscribe a webhook

    Point your number’s events at your own URL.

  3. 03

    Send your first message

    Call the campaign endpoint with an approved template.

  4. 04

    Go live

    Move from testing to production traffic.

FAQ

Developer questions

How do I get API access?

Log in to your Indew panel and create a developer token, or ask your account manager. The full token is shown only once — store it safely.

Which formats are supported?

JSON over HTTPS. Campaigns can also be sent as multipart form data with a CSV file.

Can I manage my clients’ accounts?

Yes. A master token can act for any account under you by passing its username, and you can issue account tokens for individual clients.

Do I get webhooks for bot replies?

Yes. Replies sent by chatbots and automations arrive on your webhook as message_echoes events, so your inbox stays complete.

Ready to integrate?

Tell us what you are building — we’ll set up your tokens, a test number and the full API documentation.

Chat with us