Instagram API

Instagram API: comments by REST, DMs through MCP.

Q: How do I check my Instagram permissions before replying?

Call GET /channels/{channel}/permissions with your connected Instagram channel. The response tells you whether comment permissions are granted and lists any missing scopes, so your automation can stop before a reply fails.

Read new comments, answer in public, send a private reply and keep the conversation going in DMs. Made for builders and vibe coders. Prefer WhatsApp? Put a link to your number in the reply.

In the APIComments: list, reply, private reply, permissions

Start free See the comments docs

Last updated 28 October 2026

What the Instagram API covers today

Capability	How you use it	Status
Comments: list posts and comments, reply in public	REST API	Live
Private reply to a comment	REST API	Live
DM: send and receive	MCP server	Live via MCP
DM	REST API	Coming soon, waitlist

Not supported yet: hiding or deleting comments, and Instagram webhook events.

16,000+businesses in 190+ countries
4.6/5average rating on G2
OfficialMeta Business Partner and WhatsApp BSP

One comment. One more conversation.

Answer in public, reply in private and keep talking in DMs. Or move the chat to WhatsApp.

Starts with a templateAn approved template opens the conversation, for one customer or 10,000.
Continues in chatText, media and buttons once the customer replies.
Ends with your teamWebhooks tell your code. The team inbox tells your people.

The product

Send. Reply. Hear back. Hand off.

InstagramInstagram comments and DMs

Build Instagram automation too.

List comments on your posts, reply in public or send a private reply.

Broadcasts

Personal messages, sent at scale.

Pick an approved template and pass up to 10,000 recipients. Each person gets their own variables, and each result comes back by number.

Messaging

Reply with more than text.

Inside the 24-hour window, send text, images, files, reply buttons and list pickers, with a typing indicator while you work.

Order updates and alerts

The right update, when it happens.

Your store, booking or billing system sends an approved template when something changes. Customers tap a button or reply.

Auto-reply and chatbots

Your code answers.

The message webhook brings each new message to your server. Reply with the send endpoints, or start a Wati chatbot on Pro and Business.

Webhooks

Every reply, the moment it lands.

Webhooks push new messages, read receipts, clicks and failures to your URL. No polling.

Team inbox

Code starts it. People finish it.

Replies land in the Wati team inbox. Assign an operator, set status and add tags by API, so the right person picks it up.

Contacts and segments

Your CRM, mirrored in Wati.

Create and update contacts with custom attributes, then preview a segment before you message it.

Get started

Live in three steps.

Connect
Connect your number
Link your WhatsApp number through Meta's Embedded Signup inside Wati.
Authenticate
Get a token
Create an API token in Wati and give it only the scopes you need. Keep it on your server.
Send
Make your first call
Send an approved template with one request. Then add a webhook to follow delivery.

Your first request, explained

Here is what goes into one request, and where each part shows up in the message.

Who
The customer's WhatsApp number, with country code.
phone_number14155552671
Which message
The name of a template that Meta has approved in your account.
template_nameorder_update
What to fill in
The values for the blanks in the template, one per person.
custom_paramsname = Mayaorder_id = 10482
Your key
Your API token, sent with every request. Keep it on your server.
Authorization: Bearer <token>
What you get back
A 200 means Wati accepted the message, with a broadcast_id. Delivered and read arrive later by webhook.
200broadcast_id

The message text and order_update are examples. Your approved template sets the wording.

Which comment
The comment you are answering. You get its ID when you list a post's comments.
comment_idin the URL path
From which account
Your Instagram account connected to Wati.
channel
To whom
The person who wrote the comment, taken from the same comment.
userIduserName
What to send
Plain text up to 1,000 characters, or a template with buttons.
type = texttexttype = template
What you get back
A 200 with ok set to true means the private reply went through. Use the same Authorization header as every other call.
ok: trueresult: success

POST /api/ext/v3/comments/{comment_id}/privateReply. The comment and reply text are examples. See the request in the docs

Copy-ready codeHide the code

POST/api/ext/v3/messageTemplates/send
curl -X POST "https://live-mt-server.wati.io/api/ext/v3/messageTemplates/send" \
  -H "Authorization: Bearer $WATI_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "template_name": "order_update",
    "broadcast_name": "order_update_api",
    "recipients": [
      {
        "phone_number": "14155552671",
        "custom_params": [
          { "name": "name", "value": "Maya" },
          { "name": "order_id", "value": "10482" }
        ]
      }
    ]
  }'const res = await fetch("https://live-mt-server.wati.io/api/ext/v3/messageTemplates/send", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.WATI_API_TOKEN}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    template_name: "order_update",
    broadcast_name: "order_update_api",
    recipients: [
      {
        phone_number: "14155552671",
        custom_params: [
          { name: "name", value: "Maya" },
          { name: "order_id", value: "10482" },
        ],
      },
    ],
  }),
});

console.log(await res.json());import os
import requests

resp = requests.post(
    "https://live-mt-server.wati.io/api/ext/v3/messageTemplates/send",
    headers={"Authorization": f"Bearer {os.environ['WATI_API_TOKEN']}"},
    json={
        "template_name": "order_update",
        "broadcast_name": "order_update_api",
        "recipients": [
            {
                "phone_number": "14155552671",
                "custom_params": [
                    {"name": "name", "value": "Maya"},
                    {"name": "order_id", "value": "10482"},
                ],
            }
        ],
    },
    timeout=30,
)
print(resp.json())200 Example responseShape from the docs example
{
  "success": true,
  "broadcast_id": "broadcast_123456",
  "recipients": [
    {
      "local_message_id": "local-msg-123",
      "phone_number": "14155552671",
      "errors": []
    }
  ]
}
POST/api/ext/v3/conversations/messages/text
curl -X POST "https://live-mt-server.wati.io/api/ext/v3/conversations/messages/text" \
  -H "Authorization: Bearer $WATI_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "target": "14155552671",
    "text": "Your order 10482 is out for delivery. Reply here to change the address."
  }'const res = await fetch("https://live-mt-server.wati.io/api/ext/v3/conversations/messages/text", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.WATI_API_TOKEN}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    target: "14155552671",
    text: "Your order 10482 is out for delivery. Reply here to change the address.",
  }),
});

console.log(await res.json());import os
import requests

resp = requests.post(
    "https://live-mt-server.wati.io/api/ext/v3/conversations/messages/text",
    headers={"Authorization": f"Bearer {os.environ['WATI_API_TOKEN']}"},
    json={
        "target": "14155552671",
        "text": "Your order 10482 is out for delivery. Reply here to change the address.",
    },
    timeout=30,
)
print(resp.json())200 Example responseDocs example, trimmed
{
  "message": {
    "id": "507f1f77bcf86cd799439011",
    "type": "text",
    "text": "Your order 10482 is out for delivery. Reply here to change the address.",
    "owner": true,
    "local_message_id": "88aed3c93a050b3c53978463",
    "conversation_id": "685bd235e6119686e693a093",
    "created": "2026-07-14T16:15:38.3992421Z",
    "event_type": "message"
  }
}
WEBHOOKmessage event in, POST /api/ext/v3/conversations/messages/text out
# 1. Wati POSTs each new message to your webhook URL (event: message).
# 2. Your code picks the answer and sends it back:
curl -X POST "https://live-mt-server.wati.io/api/ext/v3/conversations/messages/text" \
  -H "Authorization: Bearer $WATI_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "target": "14155552671",
    "text": "Yes, we are open from 9am to 9pm."
  }'import express from "express";

const app = express();
app.use(express.json());

app.post("/wati", async (req, res) => {
  res.sendStatus(200); // answer Wati first; it retries when it gets no 200
  const event = req.body;
  if (event.eventType !== "message" || event.owner) return; // customer messages only

  const answer = /open|hours/i.test(event.text || "")
    ? "Yes, we are open from 9am to 9pm."
    : "Thanks! A teammate will reply shortly.";

  await fetch("https://live-mt-server.wati.io/api/ext/v3/conversations/messages/text", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.WATI_API_TOKEN}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({ target: event.waId, text: answer }),
  });
});

app.listen(3000);import os
import re
import requests
from flask import Flask, request

app = Flask(__name__)

@app.post("/wati")
def wati_webhook():
    event = request.get_json(silent=True) or {}
    if event.get("eventType") == "message" and not event.get("owner"):
        text = event.get("text") or ""
        answer = (
            "Yes, we are open from 9am to 9pm."
            if re.search("open|hours", text, re.I)
            else "Thanks! A teammate will reply shortly."
        )
        requests.post(
            "https://live-mt-server.wati.io/api/ext/v3/conversations/messages/text",
            headers={"Authorization": f"Bearer {os.environ['WATI_API_TOKEN']}"},
            json={"target": event["waId"], "text": answer},
            timeout=30,
        )
    return "", 200IN What Wati posts to your URLFields from the docs example, trimmed
{
  "eventType": "message",
  "id": "69282478274a880fe782b2d9",
  "conversationId": "68c8d56157578adb12ada249",
  "waId": "14155552671",
  "senderName": "Maya",
  "type": "text",
  "text": "Are you open tomorrow?",
  "owner": false,
  "timestamp": "1764238453"
}
POST/api/ext/v3/chatbots/start
curl -X POST "https://live-mt-server.wati.io/api/ext/v3/chatbots/start" \
  -H "Authorization: Bearer $WATI_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "target": "14155552671",
    "chatbot_id": "607f1f77bcf86cd799439011"
  }'const res = await fetch("https://live-mt-server.wati.io/api/ext/v3/chatbots/start", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.WATI_API_TOKEN}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    target: "14155552671",
    chatbot_id: "607f1f77bcf86cd799439011", // from GET /chatbots
  }),
});

console.log(await res.json());import os
import requests

resp = requests.post(
    "https://live-mt-server.wati.io/api/ext/v3/chatbots/start",
    headers={"Authorization": f"Bearer {os.environ['WATI_API_TOKEN']}"},
    json={
        "target": "14155552671",
        "chatbot_id": "607f1f77bcf86cd799439011",  # from GET /chatbots
    },
    timeout=30,
)
print(resp.json())200 Example responseDocs example. Pro and Business plans
{
  "result": true
}
POST/api/ext/v3/contacts
curl -X POST "https://live-mt-server.wati.io/api/ext/v3/contacts" \
  -H "Authorization: Bearer $WATI_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "whatsapp_number": "14155552671",
    "name": "Maya",
    "custom_params": [
      { "name": "city", "value": "Singapore" },
      { "name": "customer_tier", "value": "vip" }
    ]
  }'const res = await fetch("https://live-mt-server.wati.io/api/ext/v3/contacts", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.WATI_API_TOKEN}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    whatsapp_number: "14155552671",
    name: "Maya",
    custom_params: [
      { name: "city", value: "Singapore" },
      { name: "customer_tier", value: "vip" },
    ],
  }),
});

console.log(await res.json());import os
import requests

resp = requests.post(
    "https://live-mt-server.wati.io/api/ext/v3/contacts",
    headers={"Authorization": f"Bearer {os.environ['WATI_API_TOKEN']}"},
    json={
        "whatsapp_number": "14155552671",
        "name": "Maya",
        "custom_params": [
            {"name": "city", "value": "Singapore"},
            {"name": "customer_tier", "value": "vip"},
        ],
    },
    timeout=30,
)
print(resp.json())200 Example responseDocs example, trimmed
{
  "id": "507f1f77bcf86cd799439011",
  "wa_id": "14155552671",
  "name": "Maya",
  "phone": "+14155552671",
  "opted_in": true,
  "custom_params": [
    { "name": "city", "value": "Singapore" },
    { "name": "customer_tier", "value": "vip" }
  ],
  "channel_type": "whatsapp"
}
POST/api/ext/v3/comments/{comment_id}/privateReply
curl -X POST "https://live-mt-server.wati.io/api/ext/v3/comments/$COMMENT_ID/privateReply" \
  -H "Authorization: Bearer $WATI_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "channel": "yourbrand",
    "userId": "17841400000000000",
    "userName": "maya",
    "type": "text",
    "text": "Hi Maya, yes we do. Chat with us on WhatsApp for shipping options."
  }'const commentId = "17900000000000000"; // from GET /posts/{post_id}/comments

const res = await fetch(`https://live-mt-server.wati.io/api/ext/v3/comments/${commentId}/privateReply`, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.WATI_API_TOKEN}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    channel: "yourbrand",
    userId: "17841400000000000",
    userName: "maya",
    type: "text",
    text: "Hi Maya, yes we do. Chat with us on WhatsApp for shipping options.",
  }),
});

console.log(await res.json());import os
import requests

comment_id = "17900000000000000"  # from GET /posts/{post_id}/comments

resp = requests.post(
    f"https://live-mt-server.wati.io/api/ext/v3/comments/{comment_id}/privateReply",
    headers={"Authorization": f"Bearer {os.environ['WATI_API_TOKEN']}"},
    json={
        "channel": "yourbrand",
        "userId": "17841400000000000",
        "userName": "maya",
        "type": "text",
        "text": "Hi Maya, yes we do. Chat with us on WhatsApp for shipping options.",
    },
    timeout=30,
)
print(resp.json())200 Example responseResponse shape from the docs schema
{
  "ok": true,
  "result": "success"
}

Built in

What Wati handles so you don't have to.

Number onboarding

Connect through Meta's Embedded Signup. The WhatsApp Business Account is registered to your business.

Template status

Approval, quality and category changes arrive as webhooks, so you know before a send fails.

Webhook retries

Up to 144 retries, every 10 minutes. If your endpoint keeps failing, Wati emails you.

Rate limits and queueing

Go too fast and you get 429 with a Retry-After header. Accepted messages wait in a queue.

Human handoff

A shared team inbox for the conversations your code should not answer alone.

Scoped API tokens

v3 supports scoped tokens, so each integration gets only the access it needs.

Scheduled sends

Schedule a template send for later with one call. Wati sends it on time.

Cost estimate first

Estimate what a broadcast will cost before anything is sent.

Under the hood

The endpoints, by capability.

Templates

Start conversations with approved templates, now or scheduled.

Docs →

GET/messageTemplatesPOST/messageTemplates/sendPOST/messageTemplates/schedule

Broadcasts

Read campaign results and per-recipient status, and estimate cost first.

Docs →

GET/broadcastsGET/broadcasts/{broadcast_id}/recipientsPOST/broadcasts/estimate-cost

Messaging

Reply with text, media or buttons inside the 24-hour window.

Docs →

POST/conversations/messages/textPOST/conversations/messages/fileViaUrlPOST/conversations/messages/interactivePOST/conversations/typingIndicator

Chatbots Pro+

List your Wati chatbots and start one for a contact.

Docs →

GET/chatbotsPOST/chatbots/start

Webhooks

Manage subscriptions and list the event types you can receive.

Docs →

GET/webhooksGET/webhooks/event-typesPUT/webhooks/{id}

Contacts & segments

Sync contacts and attributes from your CRM, then target segments.

Docs →

POST/contactsPUT/contactsPOST/segments/evaluate

Team inbox

Assign an operator, change status, add or remove tags.

Docs →

PUT/conversations/{target}/operatorPUT/conversations/{target}/statusPOST/conversations/{target_conv}/tags

Instagram

List posts and comments, reply in public or in private, check permissions.

Docs →

GET/posts/{post_id}/commentsPOST/comments/{comment_id}/repliesPOST/comments/{comment_id}/privateReplyGET/channels/{channel}/permissions

Paths are relative to https://live-mt-server.wati.io/api/ext/v3. Creating a webhook uses the legacy path POST /{tenantId}/api/v2/webhookEndpoints.

For AI agents, the Wati MCP server covers the same WhatsApp actions, and can reply to Instagram DMs and Messenger chats with text.

See all 19 WhatsApp webhook event types

Messages

message
newContactMessageReceived
sessionMessageSent_v2
templateMessageSent_v2

Delivery status

sentMessageDELIVERED_v2
sentMessageREAD_v2
sentMessageREPLIED_v2
templateMessageFailed

Templates and account

templateReviewed
templateQualityUpdated
templateCategoryUpdated
wabaStatusReviewUpdate
PhoneNumberQualityUpdatedEvent
accountUpdated
accountDeleted
phoneNumberDeleted

Engagement and calls

chatbotTriggered
ctaUrlClicked
call.status

BSUID versions of several events are also available. Webhook docs

Limits and plans

Clear limits. Published.

30 to 100 per 10 s

Template sends

Calls to send templates, depending on your plan (Growth, Pro or Business).

10,000 recipients

Per v3 send call

One template, up to 10,000 people, each with their own variables.

24 h window

Free-form replies

Text, media and buttons need an open customer service window. Outside it, send a template.

429 Retry-After

When you go too fast

Wati tells you how long to wait. Accepted messages are processed in a queue.

Rate limits and plan availability in detail

Documented rate limits by plan
Endpoint	Growth	Pro	Business
`/addContact`, `/getContacts`	10 / 10 s	10 / 10 s	10 / 10 s
`/getMessages`	10 / 10 s	10 / 10 s	10 / 10 s
`/sendTemplateMessage`	30 / 10 s	60 / 10 s	100 / 10 s
`/sendTemplateMessages`	30 / 10 s	60 / 10 s	100 / 10 s

Limits as published on Errors & Rate Limits, listed by endpoint name. The v1 bulk call takes up to 1,000 contacts. Core messaging, template and contact endpoints are on every plan. Team assignment, chat status, chatbots and custom segments need Pro or Business. Updating attributes for many contacts at once needs Business. Endpoint availability by plan. For higher limits, talk to Wati about your use case.

Explore the Wati API

FAQ

Questions people ask

The full API reference is public. Read the docs

What can the Wati Instagram API do?

Today the API lists your Instagram posts and their comments, returns unread comment counts, replies to comments in public, sends the commenter a private reply, and checks your account's comment permissions. Public replies can be up to 2,200 characters and private text replies up to 1,000.

Can I build Instagram automation without a big engineering team?

Yes. The comment endpoints are plain REST calls with a bearer token, so an AI app builder can write them from a short description. A good first build: check for new comments, reply in public, then send a private reply. If you already use an AI agent, the Wati MCP server can reply to Instagram DMs with text.

How do I check my Instagram permissions before replying?

Call GET /channels/{channel}/permissions with your connected Instagram channel. The response tells you whether comment permissions are granted and lists any missing scopes, so your automation can stop before a reply fails.

Do I need to know how to code?

Less than you used to. AI app builders can write the API calls from plain-English instructions, and the examples on this page show each call.

You still need a WhatsApp number connected to Wati, an API token, and a template that Meta has approved before you can start a conversation. If an AI tool writes the code, check that your token stays on the server.

What are the API rate limits?

Contact and message-history calls are limited to 10 requests per 10 seconds on every plan. Template sends are limited to 30, 60 or 100 requests per 10 seconds on Growth, Pro and Business. When you hit a limit you get HTTP 429 with a Retry-After header. For higher limits, contact Wati.

Can I message a customer at any time?

On WhatsApp, free-form text, media and interactive messages need an open 24-hour customer service window. Outside that window, start the conversation with a template that Meta has approved.

What is the difference between the WhatsApp Business app and the API?

The Business app is for manual chats on a phone, with up to 5 linked devices and broadcast lists capped at 256 contacts. The API connects WhatsApp to your own systems. You can send approved templates at volume, automate replies, receive webhooks and share one number across a team inbox.

Which endpoints are on my plan?

Core messaging, template and contact endpoints are on every plan. Team assignment, chat status, chatbots and custom segments need Pro or Business. The docs list endpoint availability by plan.