Logo NakWasap Nakwasap.my
MCP 94 tool. Sambungkan AI agent anda terus ke WhatsApp.94 tools. Plug your AI agent straight into WhatsApp.

WhatsApp anda,Your WhatsApp,
di sebalik behind kodyour anda. code.

REST API untuk hantar dan baca, webhook bertandatangan untuk setiap peristiwa, dan MCP server penuh supaya Claude, ChatGPT atau n8n boleh mengendalikan WhatsApp anda terus. Bearer token, JSON, tanpa panggilan jualan.A REST API for sending and reading, signed webhooks for everything that happens, and a full MCP server so Claude, ChatGPT or n8n can operate your WhatsApp directly. Bearer token, JSON, no sales call.

11 endpoint REST11 REST endpoints 6 event webhook6 webhook events 94 tool MCP94 MCP tools 60 req/min
Kod andaYour code curl · fetch · mana-mana runtimecurl · fetch · any runtime AI agent Claude · ChatGPT · n8n NakWasap api/v1 60 req/min WhatsApp WhatsApp Web atau WABAWhatsApp Web or WABA URL webhook andaYour webhook URL Bertandatangan HMAC-SHA256HMAC-SHA256 signed POST /api/v1/send MCP · 94 tools send message.received

Hantar mesej pertama anda dalam 60 saat.Send your first message in 60 seconds.

Jana key di Settings → Developers. Kemudian:Generate a key in Settings → Developers. Then:

curl -X POST https://nakwasap.my/api/v1/send \
  -H "Authorization: Bearer sk_live_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "instanceName": "my-device",
    "number": "60123456789",
    "type": "text",
    "text": "Hi from my app"
  }'
ResponsResponse
{ "success": true, "data": { "key": { "id": "..." } } }
Bila anti-ban queue aktifWhen the anti-ban queue is active
{ "success": true, "queued": true, "queueId": "..." }

queued: true bermakna dah masuk queue dan akan dihantar ikut pacing. JANGAN resend — kau akan hantar dua kali.means it is queued and will send at the pacing rate. Do NOT resend — you will send twice.

Pilih satu permukaan.Pick a surface.

Lapan jalan masuk ke NakWasap. Buka satu untuk lihat endpoint, event, scope dan kod.Eight ways into NakWasap. Open one to see endpoints, events, scopes and code.

REST API

Sebelas endpoint. Tanpa upacara.Eleven endpoints. Zero ceremony.

Tiada client library untuk dipasang, tiada schema untuk dikompil. API yang dashboard kami sendiri guna ialah API yang anda dapat.No client library to install, no schema to compile. The API our own dashboard runs on is the API you get.

11
EndpointEndpoints
60
req/min
—Bearer auth dengan key sk_live_, dijana dan dibatalkan dalam dashboardBearer auth with sk_live_ keys, generated and revoked in the dashboard
—Dua enjin di sebalik satu panggilan — tidak rasmi (WhatsApp Web) atau WABA rasmi, /send mengesan yang mana dan menghalakannyaBoth engines behind one call — unofficial (WhatsApp Web) or official WABA, /send detects which and routes it
—Hantar ke group melalui JID, bukan DM sahajaGroup sending by JID, not just DMs
—Media melalui URL, tiada muat naik multipart untuk dilayanMedia by URL, no multipart uploads to wrestle with
—Mendokumenkan diri — GET /api/v1/docs memulangkan parameter, contoh dan kod respons untuk setiap endpointSelf-documenting — GET /api/v1/docs returns params, examples and response codes for every endpoint
—Header had kadar pada setiap respons, jadi anda tak perlu tekaRate limit headers on every response, so you never guess
PengurusanManagement
GET /api/v1/instancesPeranti + status langsung, profil, nomborDevices + live status, profile, number
GET /api/v1/instances/qrKod QR (PNG base64) untuk sambung perantiQR code (base64 PNG) to link a device
GET /api/v1/groupsGroup untuk satu peranti — jid, nama, pesertaGroups for a device — jid, name, participants
PemesejanMessaging
POST /api/v1/sendteks · imej · video · dokumen · audio · templat. Ke satu nombor atau JID group.text · image · video · document · audio · template. To a number or a group JID.
POST /api/v1/send-templateTemplat WABA, sokongan komponen penuhWABA templates, full component support
WABA
GET /api/v1/templatesTemplat anda + status kelulusanYour templates + approval status
POST /api/v1/templates/syncTarik yang terkini dari Meta dan upsertPull latest from Meta and upsert
GET /api/v1/session-windowAdakah tetingkap 24 jam masih terbuka?Is the 24-hour window still open?
GET /api/v1/statusKesihatan akaun, penarafan kualiti, tier penghantaran, luput token, webhook terakhirAccount health, quality rating, send tier, token expiry, last webhook
DataData
GET /api/v1/contactsBerhalaman, boleh dicari, dengan stage + tagPaginated, searchable, with stage + tags
GET /api/v1/chatsBerhalaman, dengan mesej terakhir + kiraan belum dibacaPaginated, with last message + unread count
RujukanReference
GET /api/v1/docsKeseluruhan rujukan API, dalam JSONThe entire API reference, as JSON
Hantar templat dengan imej headerSend a template with a header image
curl -X POST https://nakwasap.my/api/v1/send-template \
  -H "Authorization: Bearer sk_live_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "instanceName": "waba-main",
    "number": "60123456789",
    "templateName": "order_shipped",
    "templateLanguage": "ms",
    "variables": {
      "1": "Farhan",
      "2": "NW-10294",
      "header_image": "https://cdn.example.com/parcel.jpg"
    }
  }'

Key bernombor dipetakan kepadaNumbered keys map to {{1}}, {{2}}. Key bernama mengendalikan bahagian sukar — header_image, header_video, header_document, card_1_image untuk carousel, coupon_code, lto_expiry_hours, catalog_product_id, button_url.. Named keys handle the hard parts — header_image, header_video, header_document, card_1_image for carousels, coupon_code, lto_expiry_hours, catalog_product_id, button_url.

FAQ

Yang mana saya guna — REST atau MCP?Which do I use — REST or MCP?
REST jika kod anda yang memandu. MCP jika AI atau alat automasi yang memandu. Workspace sama, data sama, key sama berfungsi untuk kedua-duanya.REST if your code drives it. MCP if an AI or an automation tool drives it. Same workspace, same data, same key works for both.
Perlukah saya akaun WhatsApp Business API rasmi?Do I need an official WhatsApp Business API account?
Tidak. Imbas QR dan anda terus hidup. Jika kemudian berpindah ke WABA, /api/v1/send kekal bentuk yang sama — kami halakan untuk anda.No. Scan a QR and you're live. If you later move to WABA, /api/v1/send keeps the same shape — we route it for you.
Adakah API akan menyebabkan nombor saya disekat?Will the API get my number banned?
Penghantaran boleh melalui anti-ban queue kami, yang mengatur rentak. Sebab itu respons mungkin pulang queued: true dan bukan sent. Hormatinya dan jangan hantar semula.Sends can run through our anti-ban queue, which paces delivery. That's why a response may come back queued: true instead of sent. Respect it and don't resend.
Boleh saya baca mesej pelanggan?Can I read customer messages?
Hanya jika anda benarkan. Pembacaan mesej ialah suis berasingan setiap key dan setiap app yang disambung, tertutup secara lalai untuk apa-apa yang anda belum luluskan.Only if you allow it. Message reading is a separate toggle per key and per connected app, off-limits by default for anything you haven't approved.
Apa jadi bila peranti saya terputus?What happens when my device disconnects?
Anda dapat webhook instance.status_changed, dan /api/v1/instances melaporkan status langsung. Kempen berhenti sementara dan bukan gagal secara senyap.You get an instance.status_changed webhook, and /api/v1/instances reports live status. Campaigns pause instead of failing silently.
Had kadar?Rate limits?
60 permintaan seminit pada REST API, dengan baki kiraan pada setiap respons. Setiap peranti juga ada had penghantaran harian.60 requests per minute on the REST API, with the remaining count on every response. Each device also has a daily send cap.
Boleh saya white-label keseluruhannya?Can I white-label the whole thing?
Boleh, termasuk dokumentasi dan nama MCP server itu sendiri.Yes, including the docs and the MCP server's own name.

Key dalam satu klik. Mesej pertama dalam enam puluh saat.Key in one click. First message in sixty seconds.

Tiada barisan kelulusan, tiada panggilan jualan, tiada pelan minimum untuk lihat API.No approval queue, no sales call, no minimum plan to see the API.