API Overview
Welcome to the eTrend Gigs API documentation. Our API allows developers, agencies, and resellers to programmatically interact with the eTrend Gigs platform — creating campaigns, placing orders, checking status, requesting refills, cancelling orders, and managing balances without needing to log into the dashboard every time.
This is useful for social media marketing (SMM) panels, agencies managing multiple client accounts, and developers building tools on top of our platform. Every order you place through the API is completed by real freelancers in the eTrend Gigs community — the same community that powers our website.
Authentication
Every request to the eTrend Gigs API must include your personal API key. You can generate an API key from your account settings after logging in.
Your API key identifies your account and authorises all requests made using it. Treat it like a password — never share your API key publicly, and never commit it to a public code repository. If you believe your API key has been compromised, regenerate it immediately from your profile page.
Get Your API KeyIncluding Your Key
Your API key must be included in the body of every request as the key parameter. Requests without a valid key will be rejected.
Request Format
HTTP Method
All requests to the eTrend Gigs API must use the POST method. We do not support GET requests because sensitive information (such as your API key) should not be passed through URLs.
Request Body
All requests must be sent as application/json. Include the appropriate parameters for the action you want to perform.
Response Format
All responses are returned in JSON format. Each endpoint returns a specific set of fields, which are described in the sections below.
Base URL
All API requests should be sent to the following base URL:
https://etrendgigs.com/api/v2
Always use https:// for secure transmission. Requests sent over plain HTTP will be redirected or rejected.
Available Services
To retrieve a full list of services currently available on the platform — including pricing, minimum and maximum quantities, and refill settings — send the following request:
Request
{
"key": "YOUR_API_KEY",
"action": "services"
}
Response Example
[
{
"service": 1,
"name": "Followers",
"type": "Default",
"category": "Social Media",
"rate": "0.90",
"min": "50",
"max": "10000",
"refill": true,
"cancel": true
},
{
"service": 2,
"name": "Comments",
"type": "Custom Comments",
"category": "Social Media",
"rate": "8",
"min": "10",
"max": "1500",
"refill": false,
"cancel": true
}
]
Response Fields
| Field | Description |
|---|---|
| service | The unique ID of this service (use this when placing an order). |
| name | The human-readable name of the service. |
| type | The order type (see Add Order for the full list). |
| category | The category the service belongs to. |
| rate | The price per unit (in NGN, the currency shown on your account). |
| min | Minimum quantity you can order in a single request. |
| max | Maximum quantity you can order in a single request. |
| refill | Whether the service supports automatic refill if numbers drop. |
| cancel | Whether an in-progress order can be cancelled. |
Add Order
To place a new order, send the service ID, the target link, and the required parameters for that service's order type. Use the dropdown below to see the exact parameters required for each order type.
Select Order Type
Default type: Default
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
| quantity | Needed quantity |
| runs optional | Runs to deliver |
| interval optional | Interval in minutes |
Package type: Package
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
Custom Comments type: Custom Comments
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
| comments | Comments list separated by \r\n or \n |
Mentions with Hashtags type: Mentions with Hashtags
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
| quantity | Needed quantity |
| usernames | Usernames list separated by \r\n or \n |
| hashtags | Hashtags list separated by \r\n or \n |
Mentions Custom List type: Mentions Custom List
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
| usernames | Usernames list separated by \r\n or \n |
Mentions Hashtag type: Mentions Hashtag
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
| quantity | Needed quantity |
| hashtag | Hashtag to scrape usernames from |
Mentions User Followers type: Mentions User Followers
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
| quantity | Needed quantity |
| username | URL to scrape followers from |
Mentions Media Likers type: Mentions Media Likers
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
| quantity | Needed quantity |
| media | Media URL to scrape likers from |
Custom Comments Package type: Custom Comments Package
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
| comments | Comments list separated by \r\n or \n |
Comment Likes type: Comment Likes
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
| quantity | Needed quantity |
| username | Username of the comment owner |
Poll type: Poll
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
| quantity | Needed quantity |
| answer_number | Answer number of the poll |
Invites from Groups type: Invites from Groups
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| link | Link to page |
| quantity | Needed quantity |
| groups | Groups list separated by \r\n or \n |
Subscriptions type: Subscriptions
| Parameters | Description |
|---|---|
| key | Your API key |
| action | add |
| service | Service ID |
| username | Username |
| min | Quantity min |
| max | Quantity max |
| posts optional | Limit the number of new (future) posts that will be parsed and for which orders will be created. If not set, the subscription is created for an unlimited number of posts. |
| old_posts optional | Number of existing posts that will be parsed and for which orders will be created (if this option is available for the service). |
| delay | Delay in minutes. Possible values: 0, 5, 10, 15, 20, 30, 40, 50, 60, 90, 120, 150, 180, 210, 240, 270, 300, 360, 420, 480, 540, 600 |
| expiry optional | Expiry date. Format d/m/Y |
Example Response
{
"order": 23501
}
order value in the response is your unique order ID. Save it — you will need it to check the status of the order later. Orders are deducted from your account balance at the time of submission.
Order Status
To check the current status of any order you have placed, send the order ID using the status action.
Request
{
"key": "YOUR_API_KEY",
"action": "status",
"order": "ORDER_ID"
}
Response Example
{
"charge": "0.27819",
"start_count": "3572",
"status": "Partial",
"remains": "157",
"currency": "NGN"
}
Response Fields
| Field | Description |
|---|---|
| charge | The total amount charged for this order. |
| start_count | The count on the target at the moment the order started. |
| status | Current state of the order. Possible values: Pending, In progress, Completed, Partial, Canceled. |
| remains | The number of units still to be delivered. |
| currency | The currency used for the charge (NGN). |
Multiple Order Status
To check the status of up to 100 orders in a single request, send comma-separated order IDs using the orders parameter.
Request
{
"key": "YOUR_API_KEY",
"action": "status",
"orders": "1,10,100"
}
Response Example
{
"1": {
"charge": "0.27819",
"start_count": "3572",
"status": "Partial",
"remains": "157",
"currency": "NGN"
},
"10": {
"error": "Incorrect order ID"
},
"100": {
"charge": "1.44219",
"start_count": "234",
"status": "In progress",
"remains": "10",
"currency": "NGN"
}
}
error field instead of the status object — the rest still succeed.
Refill
If a service supports refill, you can request a refill for one or multiple orders. The order must be eligible (i.e. the service has refill: true in the services list, and the order is in a state that allows refill).
Create Refill
| Parameters | Description |
|---|---|
| key | Your API key |
| action | refill |
| order | Order ID |
{
"refill": "1"
}
Create Multiple Refill
| Parameters | Description |
|---|---|
| key | Your API key |
| action | refill |
| orders | Order IDs (separated by a comma, up to 100 IDs) |
[
{
"order": 1,
"refill": 1
},
{
"order": 2,
"refill": 2
},
{
"order": 3,
"refill": {
"error": "Incorrect order ID"
}
}
]
Refill Status
Once a refill has been created, use these endpoints to check its status. Refill status values include Pending, In progress, Completed, Rejected.
Get Refill Status
| Parameters | Description |
|---|---|
| key | Your API key |
| action | refill_status |
| refill | Refill ID |
{
"status": "Completed"
}
Get Multiple Refill Status
| Parameters | Description |
|---|---|
| key | Your API key |
| action | refill_status |
| refills | Refill IDs (separated by a comma, up to 100 IDs) |
[
{
"refill": 1,
"status": "Completed"
},
{
"refill": 2,
"status": "Rejected"
},
{
"refill": 3,
"status": {
"error": "Refill not found"
}
}
]
Cancel Orders
If a service allows cancellation (i.e. cancel: true in the services list), you can cancel one or more orders using the cancel action. Only orders that have not started delivery can usually be cancelled.
Request
| Parameters | Description |
|---|---|
| key | Your API key |
| action | cancel |
| orders | Order IDs (separated by a comma, up to 100 IDs) |
Response Example
[
{
"order": 9,
"cancel": {
"error": "Incorrect order ID"
}
},
{
"order": 2,
"cancel": 1
}
]
"cancel": 1. If the order cannot be cancelled, the response for that order contains an error object explaining why.
User Balance
To check the current balance of your eTrend Gigs wallet, send the following request.
Request
{
"key": "YOUR_API_KEY",
"action": "balance"
}
Response Example
{
"balance": "100.84292",
"currency": "NGN"
}
Error Handling
If a request fails, the API returns a JSON object with an error field containing a description of the problem. Common errors include:
Invalid API key — your key is missing, incorrect, or has been revoked.
Insufficient balance — your wallet does not have enough funds to cover the order.
Invalid service — the service ID you provided does not exist or is not active.
Invalid link — the target link is malformed or not accepted by the service.
Quantity out of range — the quantity you requested is below the minimum or above the maximum for that service.
Incorrect order ID — the order ID you provided does not exist or is not owned by your account.
Refill not found — the refill ID does not exist.
Cannot cancel — the order has already started or cannot be cancelled.
When you receive an error, do not retry the same request repeatedly without fixing the underlying issue — repeated failed requests may be rate-limited.
Support & Contact
If you are stuck, or if you need help integrating the API into your application, our support team can help. Please include the specific request you made and any error response you received so we can assist you more quickly.
Email: [email protected]
Contact page: etrendgigs.com/contact
WhatsApp: +234 7031 280 387 (messages only)