N Noqou Managed Instagram DM API
Log in View docs Book a call
Production today, live sends, real webhooks

Programmatic Instagram outreach.
Zero sender ops.

POST targets and a message template. We run sender accounts, proxies, sessions, and limits. You get webhooks when creators are contacted or reply.

Book a scoping call See API docs
You POST campaignstargets, template, limits
We run Instagramsenders, proxies, sessions
You get webhookson every outcome
campaign.request Prod webhook example
POST /api/v1/campaigns
PUT  /api/v1/campaigns/6/webhook
POST /api/v1/campaigns/6/activate
{
  "name": "Creator outreach",
  "targets": ["nivelimpactmarketing"],
  "message_template": "hey {username}, collab idea"
}
webhook fires dm.sent
{
  "event": "dm.sent",
  "campaign_id": 6,
  "job_id": 5,
  "account_id": 4,
  "target_username": "nivelimpactmarketing",
  "result": "success",
  "timestamp": "2026-06-22T09:20:44.872782"
}
The messaging-infrastructure pattern, applied to Instagram DMs.
4webhook events
0accounts you manage
REST+ webhooks
CSVexport + analytics
What are you building?

One outreach layer, three ways to plug in.

{ }

AI agent / automation team

Give your agent an outreach action. It POSTs a campaign, we run Instagram, results stream back as webhooks.

Wire it into a workflow →

Agency / growth team

Run creator and affiliate recruitment at volume. Upload targets, set limits, track replies. No accounts to babysit.

Run a recruitment campaign →
</>

Developer

A REST API and signed webhooks. No browser automation, no session code, no proxy rotation to maintain.

Read the API reference →
How it works

You POST campaigns. We run Instagram. You get webhooks.

01

POST a campaign

Targets, message template, limits, then a webhook URL on a separate call. That is your entire integration.

02

We operate Instagram

Sender accounts, residential proxies, session stability, throttling, account health, and failover when a sender is limited.

03

You get events

Webhooks on every outcome, plus campaign analytics and CSV export. Reconcile against your own system in real time.

The API

Three calls, then you listen.

Create a campaign, configure your webhook URL, activate sending, then handle events as they fire. No polling, no scraping, no headless browser in your stack.

POST/api/v1/campaigns
PUT/api/v1/campaigns/{id}/webhook
POST/api/v1/campaigns/{id}/activate
Webhook events
dm.sent dm.failed dm.replied campaign.completed
# 1. Create campaign (draft)
curl -X POST https://api.noqou.com/api/v1/campaigns \
  -H "X-API-Key: $NOQOU_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Creator outreach",
    "targets": ["nivelimpactmarketing", "creator.two"],
    "message_template": "hey {username}, quick collab idea",
    "tos": {
      "version": "2026-06-01",
      "permission_acknowledged": true,
      "instagram_risk_acknowledged": true,
      "compliance_acknowledged": true
    }
  }'

# 2. Configure webhook
curl -X PUT https://api.noqou.com/api/v1/campaigns/6/webhook \
  -H "X-API-Key: $NOQOU_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://app.you.com/webhooks/noqou",
    "events": ["dm.sent", "dm.failed", "dm.replied", "campaign.completed"]
  }'

# 3. Activate sending
curl -X POST https://api.noqou.com/api/v1/campaigns/6/activate \
  -H "X-API-Key: $NOQOU_API_KEY"
{
  "id": 6,
  "name": "Creator outreach",
  "status": "draft",
  "message_template": "hey {username}, quick collab idea",
  "target_count": 2,
  "priority": 5
}
{
  "event": "dm.sent",
  "campaign_id": 6,
  "job_id": 5,
  "account_id": 4,
  "target_username": "nivelimpactmarketing",
  "result": "success",
  "timestamp": "2026-06-22T09:20:44.872782"
}
The dividing line

What you manage vs what we manage.

You never log into Instagram. That is the whole point, and the difference between Noqou and connect-your-own-account tools.

You manage

Targets and message copy
Your webhook endpoint
Campaign strategy
Integration into your product

Noqou manages

Sender Instagram accounts
Residential proxies
Sessions and login stability
Rate limits and throttling
Health monitoring and failover
Maintenance when Instagram changes
The alternatives

Why not scripts, or connect-your-account tools?

DIY scripts
Connect-your-account
Noqou
Sender accounts provided
you
you
Noqou
Proxies and sessions
you
you
Noqou
Failover when limited
manual
manual
managed
REST API + webhooks
build it
partial
native
You maintain when IG changes
always
often
never
Reliability

We own the part that breaks.

Production today

Live sends and real webhooks, not a roadmap. The payload above is a real event shape.

Ops ownership

When a sender dies or gets challenged, we handle it and re-route. You see a clean event, not an outage.

Responsible sending

Rate limits, suppression lists, and opt-out on reply are built in. We throttle to protect deliverability.

Small team, full-time

A dedicated team on this every day, not a side project. You get operators who answer, not a ticket queue.

Pricing

Start with a pilot. Scale on the API.

Book a 20-minute scoping call. We provision API keys by hand after we align on your use case.

Pilot

One campaign, concierge setup, success criteria agreed on a call.

Scoped on call

Volume and pricing aligned together — no self-serve checkout.

~200 creators, one campaign Concierge onboarding and setup Full webhook + CSV delivery Success criteria agreed up front
Book scoping call
MOST COMMON

Production

Ongoing API access with managed senders and webhooks.

from$699–999/mo
Ongoing REST API access Managed sender fleet + failover All four webhook events Analytics + CSV export
Book scoping call

Agency

Multi-campaign, higher volume, with an SLA.

Custom
Multiple concurrent campaigns Higher send volume SLA and priority ops Dedicated point of contact
Book scoping call
FAQ

Questions a builder actually asks.

No. Noqou is managed outreach infrastructure, not a Meta product or partnership. We run a fleet of sender accounts on your behalf and expose a REST API and webhooks over it. Use it responsibly, within sane limits.
No, and that is the core difference. We operate the sender accounts, proxies, and sessions. You never log into Instagram or connect an account. You POST targets and a template, we handle the rest.
Configure a webhook URL with PUT /api/v1/campaigns/{id}/webhook. We POST signed JSON to it on every outcome: dm.sent, dm.failed, dm.replied, and campaign.completed. Reconcile in real time — no polling required.
We detect it through health monitoring and fail over to a healthy sender automatically. The job continues. You do not manage the recovery, and in most cases you only see a clean dm.sent once it completes.
No, and we would not want to. We enforce rate limits, suppression lists, and opt-out on reply to protect deliverability and keep senders healthy. Responsible, throttled outreach is what makes the fleet last.
Connect-your-account tools hand you a dashboard but still make you supply and manage the accounts. Noqou runs the sender fleet end to end. You get an API and webhooks, not a browser extension to babysit.
Book a 20-minute scoping call. Once we agree on targets and success criteria, a concierge pilot typically starts within days.
Real-time webhooks per event, campaign analytics in the dashboard, and a CSV export of every send and reply. Enough to attribute outreach to outcomes in your own reporting.

Book a pilot scoping call

20 minutes to align on targets, message, webhooks, and success criteria. We provision API keys by hand after the call.

What we cover on the call

  • Target list and campaign goal
  • Message template and webhook events
  • Pilot success criteria and timeline
  • API access and next steps
Book on Cal.com

Prefer email? Write to hello@noqou.com with your use case — we reply within a day.