notpanel
ServicesPricingFAQGiveawayAPI
notpanel

Followers, likes and views for every platform.

The catalog combines directly operated services with capacity from vetted partners. Current availability, timing, refill, and drip-feed support are shown per service; routing and partner identities remain confidential.

Product

  • Services
  • Pricing
  • Price Index
  • Affiliate Program

Resources

  • API
  • Blog
  • FAQ
  • Status

Company

  • About
  • Why NotPanel
  • Contact Us

Legal

  • Terms of Service
  • Privacy Policy
  • Refund Policy

Languages

  • English
  • Español
  • Português
  • Русский
  • Türkçe
  • العربية
  • हिन्दी
  • Bahasa Indonesia
  • Français
  • 中文

© 2026 NotPanel. All rights reserved.

support@notpanel.com
notpanel
API documentation
+
API documentation

Introduction

  • Overview
  • Getting started
  • Authentication
  • Rate limits
  • Errors

Catalog

  • List services
  • Advanced catalog
  • Service types

Orders

  • Place order
  • Order status
  • Refund quote
  • Refill
  • Cancel

Account

  • Account status
  • Balance

Webhooks

  • Manage webhooks

Reference

  • Changelog
  • SDKs & libraries

Need help?

support@notpanel.com →

List services

Returns a cached compatibility array of active services and account-priced rates. A response may be cached for up to 5 minutes. It does not expose current availability; use action=catalog for availability and richer discovery metadata. The committed action=add response is authoritative for the order charge.

POSThttps://notpanel.com/api/v3action=services
API key requiredRate limited (shared account + IP + action)Body: application/x-www-form-urlencoded

Parameters

NameTypeDescription
keyRequiredstringYour API key. Required on every request.
actionRequiredstringMust be the literal string "services".
languagelanguage codeOptional service-name language: en, es, pt, ru, tr, ar, hi, id, fr, or zh. pt is Brazilian Portuguese and zh is Simplified Chinese. Curated market terminology preserves recognizable brands and product identifiers; use the stable service ID for integration logic. Omit it to preserve the exact legacy English response shape. Admins can review or refine individual names.

Example request

Replace YOUR_API_KEY with the key generated under your dashboard’s API page.

curl -X POST https://notpanel.com/api/v3 \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "key=YOUR_API_KEY&action=services&language=hi"
const res = await fetch("https://notpanel.com/api/v3", {
  method: "POST",
  headers: { "Content-Type": "application/x-www-form-urlencoded" },
  body: new URLSearchParams({
    key: "YOUR_API_KEY",
    action: "services",
    language: "hi",
  }),
});

const data = await res.json();
console.log(data);
import requests

res = requests.post(
  "https://notpanel.com/api/v3",
  data={
    "key": "YOUR_API_KEY",
    "action": "services",
    "language": "hi",
},
)
print(res.json())
<?php
$body = http_build_query([
    'key' => 'YOUR_API_KEY',
    'action' => 'services',
    'language' => 'hi',
]);

$response = file_get_contents('https://notpanel.com/api/v3', false, stream_context_create([
    'http' => [
        'method'  => 'POST',
        'header'  => "Content-Type: application/x-www-form-urlencoded\r\n",
        'content' => $body,
        'ignore_errors' => true,
    ],
]));

print_r(json_decode($response, true));

Example response

[
  {
    "service": "1",
    "name": "Instagram रियल फॉलोअर्स",
    "canonical_name": "Instagram Followers — Real",
    "name_language": "hi",
    "type": "Default",
    "type_key": "default",
    "rate": "0.50",
    "min": "100",
    "max": "100000",
    "category": "Instagram Followers",
    "refill": true,
    "cancel": true,
    "dripfeed": true
  },
  {
    "service": "2",
    "name": "TikTok Views — High Retention",
    "canonical_name": "TikTok Views — High Retention",
    "name_language": "en",
    "type": "Default",
    "type_key": "default",
    "rate": "0.05",
    "min": "1000",
    "max": "10000000",
    "category": "TikTok Views",
    "refill": false,
    "cancel": true,
    "dripfeed": false
  }
]

Common errors

StatusBodyCause
400{"error":"Invalid API key"}Missing or unrecognised key.
403{"error":"Account suspended"}Account is not in active status.
400{"error":"language must be one of en, es, pt, ru, tr, ar, hi, id, fr, zh","error_code":"INVALID_LANGUAGE"}The language value is not supported. Use one of the ten documented service-name language codes.

Field reference

  • service — Stable numeric ID. Use this when placing an order.
  • name — Service display name in the actual language reported by name_language when localization is requested.
  • canonical_name — Stable English service name, included only when language is supplied. Use the numeric service ID—not either name—for integration logic.
  • name_language — Actual language of name, included only when language is supplied. It is en when a curated translation is missing or stale.
  • type — Familiar service label. The additive type_key supplies the stable normalized value.
  • rate — Account-facing USD per 1,000 units, formatted as a string. It is part of the cached catalog snapshot; the committed action=add result determines the order charge.
  • min, max — Order quantity bounds, inclusive.
  • category — Category display name, or the literal Uncategorized when no category is assigned.
  • refill — Whether action=refill may be requested for completed or partial orders for this service.
  • cancel — Legacy compatibility flag. It is true for every service listed by this action; use action=catalog for cancellation mode, window, and current availability.
  • dripfeed — Whether the service accepts paired runs and interval parameters for paced delivery.

Market-native service names

Localized names use curated market terminology for how buyers in each market naturally read and search, rather than translated word for word. Recognizable brands and product identifiers such as Instagram, Telegram, YouTube, service codes, URLs, handles, and hashtags remain intact. An explicit language adds canonical_name and name_language; if the requested name is missing or became stale after a canonical-name change, name safely falls back to English and name_language is en. Admins can review or refine individual names. The canonical English name is the source reference, and the numeric service ID remains the stable integration key. Omitting language keeps the legacy English fields and shape unchanged.