Neofollower-SMM-Panel-API README

The project's README from github.com/Neofollower/Neofollower-SMM-Panel-API. As one markdown file: README.md.

NeoFollower SMM Panel Reseller API

Official NeoFollower reseller API documentation, integration reference, and code examples for SMM panels, agencies, developers, and social media service resellers.

Use the NeoFollower API to retrieve available services, place reseller orders, check single or multiple order statuses, and query your account balance programmatically.

This repository is maintained as the public developer reference for the NeoFollower reseller API. Never commit your real API key to source control.

What is the NeoFollower Reseller API?

The NeoFollower Reseller API is an HTTP API for automating common SMM panel reseller workflows. A reseller can connect a website, panel, script, application, or internal automation to NeoFollower and interact with the service catalog and order system without placing every order manually.

Typical integrations include:

Quick start

Every request is sent to the same endpoint:

https://panel.neofollower.com/api/v1

Send parameters as a POST request. Your API key is passed using the key parameter and the operation is selected using action.

1. Get the service list

curl -X POST "https://panel.neofollower.com/api/v1" \
  -d "key=YOUR_API_KEY" \
  -d "action=services"

2. Place an order

curl -X POST "https://panel.neofollower.com/api/v1" \
  -d "key=YOUR_API_KEY" \
  -d "action=add" \
  -d "service=SERVICE_ID" \
  -d "link=https://example.com/post" \
  -d "quantity=100"

Example response:

{
  "status": "success",
  "order": 32
}

3. Check an order

curl -X POST "https://panel.neofollower.com/api/v1" \
  -d "key=YOUR_API_KEY" \
  -d "action=status" \
  -d "order=32"

4. Check your balance

curl -X POST "https://panel.neofollower.com/api/v1" \
  -d "key=YOUR_API_KEY" \
  -d "action=balance"

API actions

Action Purpose Main parameters
services Retrieve the current service catalog key, action
add Place a new reseller order key, action, service, service-specific fields
status Check one order key, action, order
status Check multiple orders key, action, orders
balance Retrieve account balance and currency key, action

See the complete API reference.

Code examples

Ready-to-edit examples are included for several common environments:

All examples read the API key from an environment variable where practical.

Machine-readable API definition

The repository includes an OpenAPI 3.1 definition for the core API actions. It can be imported into compatible API clients, documentation systems, developer tools, and code assistants.

Authentication

NeoFollower uses an API key supplied as the key request parameter.

key=YOUR_API_KEY

Keep API credentials server-side. Do not expose an API key in browser JavaScript, public repositories, screenshots, support posts, or frontend source code.

Request format

Requests should be sent with POST. Form-encoded requests are the simplest interoperable option:

POST /api/v1 HTTP/1.1
Host: panel.neofollower.com
Content-Type: application/x-www-form-urlencoded

key=YOUR_API_KEY&action=balance

Service-specific order payloads

Different NeoFollower services can require different order fields. Common fields exposed by the API documentation include:

service, link, quantity, runs, interval, comments, usernames, hashtags, hashtag, username, min, max, delay, and expiry.

Do not assume every field applies to every service. Retrieve the current service catalog and follow the requirements of the service you are ordering.

See service-specific payloads.

Error handling

Production integrations should:

  1. Validate required input before sending an order.
  2. Treat non-2xx responses as transport failures.
  3. Validate that the response is JSON before parsing it.
  4. Check response fields before assuming an order was created.
  5. Store the returned order ID.
  6. Poll order status responsibly instead of making rapid repeated requests.
  7. Log errors without logging API keys.

See troubleshooting and integration safety.

FAQ

What is the NeoFollower API endpoint?

The official reseller API endpoint is:

https://panel.neofollower.com/api/v1

What format does the API return?

The API returns JSON responses.

How do I authenticate?

Include your NeoFollower API key in the key parameter of each API request.

Can I retrieve NeoFollower services through the API?

Yes. Send action=services.

Can I place SMM reseller orders automatically?

Yes. Send action=add together with the service ID and the parameters required by that service.

Can I check multiple order statuses?

Yes. Use action=status and send comma-separated order IDs in the orders parameter.

Can I check my reseller balance through the API?

Yes. Send action=balance.

More answers are available in the NeoFollower API FAQ.

Repository structure

.
├── README.md
├── openapi.yaml
├── CHANGELOG.md
├── CITATION.cff
├── LICENSE
├── SECURITY.md
├── CONTRIBUTING.md
├── docs/
│   ├── api-reference.md
│   ├── service-payloads.md
│   ├── integration-guide.md
│   ├── troubleshooting.md
│   └── faq.md
├── examples/
│   ├── curl/
│   ├── php/
│   ├── python/
│   ├── javascript/
│   └── go/
└── postman/
    └── NeoFollower-Reseller-API.postman_collection.json

Support

For account, service, order, or API-key questions, use the official NeoFollower support channels available through the website or reseller panel.

For errors in this repository's documentation or examples, open a GitHub issue.

License

The documentation and example code in this repository are released under the MIT License, unless a file states otherwise.

NeoFollower — official reseller API documentation and integration examples for developers building with the NeoFollower SMM panel.

Neofollower-SMM-Panel-API (Neofollower/Neofollower-SMM-Panel-API)

Searching Database…

113 ·GitHub
Neofollower-SMM-Panel-API
Что это такое?Официальный справочник для разработчиков по API реселлера NeoFollower — это HTTP API для реселлеров SMM-панелей (продвижения в соцсетях), который автоматизирует просмотр каталога услуг, создание заказов, отслеживание статусов и проверку баланса.
Это сам API или только документация к нему?Только справочник: в репозитории лежат документация, OpenAPI 3.1-спецификация и готовые примеры кода, которые можно править под себя. Сам API — это размещённый на серверах NeoFollower эндпоинт, к которому вы обращаетесь по HTTP.
Как начать делать запросы?Получите API-ключ в панели реселлера NeoFollower, затем отправляйте POST-запросы на единственный API-эндпоинт: параметр key вас авторизует, action выбирает операцию, ответы приходят в формате JSON, а самый простой вариант — запросы с form-encoded данными.
У всех услуг одинаковые параметры для заказа?Нет — поля вроде link, quantity, runs, interval или comments различаются от услуги к услуге, поэтому загружайте актуальный каталог и ориентируйтесь на требования именно той услуги, которую заказываете, а не предполагайте, что поле подходит везде.
Можно ли проверить несколько заказов одним запросом?Да — отправьте action=status и перечислите ID заказов через запятую в параметре orders, чтобы проверить их одним пакетом.
Можно ли импортировать спецификацию API в Postman или другой API-клиент?Да — в репозитории есть OpenAPI 3.1-спецификация основных операций, которую можно импортировать в совместимые API-клиенты, системы документации и ассистенты для кода.
Что обычно строят на его основе?SMM-панели реселлеров, собственные дашборды для продвижения в соцсетях, системы управления заказами для агентств, интеграции с WordPress или WooCommerce, а также серверные скрипты и задачи по расписанию.
What are similar projects?Neofollower-SMM-Reseller-API-for-Woocommerce, posting, swagger-ui, OpenAPI-Specification, guzzle, vibex, swag, insomnia
Which topics is it in?curl, api-documentation, marketing-automation, openapi, marketing, php, http, json, documentation, developers, go, api
Creator
Neofollower
Size
<0.1 MB
Stars
113
Updated
CommitAug 20Releasev1.0.0Aug 20
Age
1mo
Commits · 90 Days