Fame Signal API Documentation
Connect your application to Fame Signal
Use the Fame Signal API to browse 28+ social media services across Instagram and Facebook, check your wallet balance, place orders, and track delivery from your own marketing scripts, bots, or custom ordering dashboards.
This guide covers authentication, the request format, all nine supported actions, order statuses, error codes, and code examples for cURL, Python, JavaScript, and PHP. It is built for developers, resellers, and agencies.
Before You Start
You'll need:
Panel Account
A Fame Signal panel account registered at panel.famesignal.com.
Secret API Key
A secret API key generated in Settings.
Funded USD Wallet Balance
A funded USD wallet balance to place orders programmatically.
HTTP Client
Any HTTP client that can send standard POST requests.
Get Your API Key
Sign in to your panel and open Settings → API Key. Your secret key is generated once, so use the one-click copy button and store it securely right away. The panel also shows your key prefix and provides rotation controls if you need a new key.
Your API key authorizes requests to your account and wallet. Keep it private and store it in a server-side environment variable or a secrets manager.
Quick Start
Start with requests that read information before testing an action that places an order.
1. Configure Authentication
Send every request as a POST to the base URL with Content-Type: application/x-www-form-urlencoded. Include key=YOUR_API_KEY in every request body.
Never include your API key in browser-side JavaScript, public repositories, screenshots, or application logs.
2. Check Your Balance
Send action=balance to verify your connection and credentials. A successful response returns your USD wallet balance:
{"balance": 991.00, "currency": "USD"}3. Retrieve Available Services
Send action=services to get the full catalog. Each service includes its service_id, service_name, minimum and maximum quantity, and starting price. Then send action=service_pricing with a service_id to get its package tiers, quantity intervals, and exact prices.
4. Submit an Order
Send action=add with the service_id, link, and quantity. Add custom_comments for services that support them. Validate the link and quantity before sending, and confirm that your wallet has enough funds.
{"order": 123456}5. Save the Order ID and Track Progress
Save the order ID against your internal record. Use action=status to check one order, or action=multiStatus to check up to 100 orders in one request.
Authentication and Request Format
Every request uses the same format:
key=YOUR_API_KEY in every request bodyProtect Your Credentials
- Store keys on your backend, outside your source code.
- Restrict access to the people and systems that need them.
- Redact credentials from logs and error reports.
- Rotate a key in Settings if it is exposed, then update every integration that uses it.
API Endpoint Reference
The API supports nine actions. Send the action name in the action parameter.
| Action | Required Parameters | What It Does |
|---|---|---|
| balance | key, action=balance | Returns your USD wallet balance. |
| services | key, action=services | Returns the full catalog of 28 services with service_id, service_name, min/max quantity, and starting price. |
| service_pricing | key, action=service_pricing, service_id | Returns available package tiers, quantity intervals, and exact prices for a service. |
| add | key, action=add, service_id, link, quantity, [custom_comments] | Submits a new order, deducts your wallet balance, and returns the order ID. |
| status | key, action=status, order | Returns status, submission_id, charge, start_count, remains, and currency. |
| multiStatus | key, action=multiStatus, orders (comma-separated, max 100) | Returns a bulk status lookup keyed by order ID. |
| refill | key, action=refill, order | Requests a 60-day refill for eligible drops. |
| refill_status | key, action=refill_status, refill | Returns the status of a refill request. |
| cancel | key, action=cancel, order | Submits a cancellation request for an eligible order. |
Check Your Balance (balance)
Retrieve your available USD wallet balance before submitting orders.
Retrieve Services (services)
Fetch the full catalog of social media services, currently covering Instagram and Facebook.
Get Service Pricing (service_pricing)
Retrieve package tiers, quantity intervals, and exact prices for a specific service_id.
Place an Order (add)
Submit the service_id, link, and quantity. Add custom_comments for services that support them.
Check One Order (status)
Retrieve the status, charge, start count, and remaining count of an existing order.
Check Multiple Orders (multiStatus)
Check up to 100 orders in one request by sending comma-separated order IDs.
Request a Refill (refill)
Request a refill for an eligible order under the 60-day refill guarantee.
Check Refill Status (refill_status)
Check the progress of a refill request using its refill ID.
Cancel an Order (cancel)
Submit a cancellation request for an eligible order.
Code Examples
Replace YOUR_API_KEY with your own key. Keep keys on your server.
cURL
Check your balance:
curl -X POST https://panel.famesignal.com/developer/api/v2/ \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "key=YOUR_API_KEY" \ -d "action=balance"
Understand Order Statuses
The status action returns status, submission_id, charge, start_count, remains, and currency. Use the exact status values below in your application logic.
Your order is queued and delivery has not started.
Delivery is underway.
Delivery has finished.
Part of the order has been delivered.
The order has been canceled.
Receiving an order ID confirms that an order was created, not that delivery has finished. Your application should:
- Store the most recent status returned by the API.
- Use start_count and remains to show delivery progress.
- Handle Partial and Canceled outcomes.
- Avoid treating an unfamiliar status as a completed order.
- Stop routine polling once an order is Completed, Partial, or Canceled.
Error Codes
Check the response body for an error code, then correct the request, wait, or contact support.
| Code | Error | What to do |
|---|---|---|
| 101 | INVALID_API_KEY | Check that you are sending the correct, current API key. |
| 102 | RATE_LIMIT_EXCEEDED | Slow down. The limit is 60 requests per minute per key. |
| 201 | INVALID_ACTION | Check the action name against the endpoint reference. |
| 202 | MISSING_REQUIRED_FIELD | Add the missing field, such as service_id or link. |
| 203 | MISSING_ORDER_ID | Include the order parameter. |
| 204 | MISSING_ORDERS_PARAM | Include the orders parameter for multiStatus. |
| 205 | INVALID_ORDER_IDS | Check the order IDs you sent. |
| 206 | TOO_MANY_ORDERS | Send no more than 100 order IDs per multiStatus request. |
| 301 | INVALID_SERVICE | Refresh the catalog and use a valid service_id. |
| 401 | QUANTITY_OUT_OF_RANGE | Use a quantity within the service's minimum and maximum. |
| 402 | INSUFFICIENT_BALANCE | Add funds to your wallet, then retry. |
| 404 | ORDER_NOT_FOUND | Check the order ID. |
| 900 | INTERNAL_ERROR | Wait and retry. Contact support if it continues. |
Handle Timeouts Safely
A timeout does not always mean an order failed to reach the server. Do not automatically repeat an add request.
Check your panel order history or use status to confirm whether the order was created. If the outcome is still unclear, contact support before retrying.
Rate Limits
Each API key can send 60 requests per minute. Requests above this limit return error 102 (RATE_LIMIT_EXCEEDED).
Use a request queue to control traffic, avoid unnecessary catalog refreshes, and use multiStatus to check up to 100 orders in one request. Choose a sensible polling interval for active orders rather than checking continuously.
Example Integration Workflow
A typical order-management application:
Frequently Asked Questions
Everything you need to know about the Fame Signal REST API integration.
Sign in to your panel and open Settings → API Key. Your secret key is generated once, so copy it right away. You can rotate it from the same page.
Start Your Integration
Generate your API key, verify authentication with a balance request, and explore the service catalog before placing your first order.