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.
- API endpoint:
https://panel.neofollower.com/api/v1 - HTTP method:
POST - Response format:
JSON - Authentication: API key in the request body
- Official website: https://neofollower.com
- Live API documentation: https://panel.neofollower.com/api/docs
This repository is maintained as the public developer reference for the NeoFollower reseller API. Never commit your real API key to source control.
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:
- SMM reseller panels
- Custom social media marketing dashboards
- Agency order-management systems
- WordPress or WooCommerce integrations
- Internal automation tools
- Server-side scripts and scheduled jobs
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.
curl -X POST "https://panel.neofollower.com/api/v1" \
-d "key=YOUR_API_KEY" \
-d "action=services"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
}curl -X POST "https://panel.neofollower.com/api/v1" \
-d "key=YOUR_API_KEY" \
-d "action=status" \
-d "order=32"curl -X POST "https://panel.neofollower.com/api/v1" \
-d "key=YOUR_API_KEY" \
-d "action=balance"| 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.
Ready-to-edit examples are included for several common environments:
All examples read the API key from an environment variable where practical.
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.
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.
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=balanceDifferent 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.
Production integrations should:
- Validate required input before sending an order.
- Treat non-2xx responses as transport failures.
- Validate that the response is JSON before parsing it.
- Check response fields before assuming an order was created.
- Store the returned order ID.
- Poll order status responsibly instead of making rapid repeated requests.
- Log errors without logging API keys.
See troubleshooting and integration safety.
The official reseller API endpoint is:
https://panel.neofollower.com/api/v1
The API returns JSON responses.
Include your NeoFollower API key in the key parameter of each API request.
Yes. Send action=services.
Yes. Send action=add together with the service ID and the parameters required by that service.
Yes. Use action=status and send comma-separated order IDs in the orders parameter.
Yes. Send action=balance.
More answers are available in the NeoFollower API FAQ.
.
├── 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
- Website: https://neofollower.com
- Reseller panel: https://panel.neofollower.com
- Live API docs: https://panel.neofollower.com/api/docs
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.
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.