ForceTrend.com API
Use the API to pull the current leaderboard into your own systems, dashboards, internal tools, research workflows, or automated reporting. API usage requires an active ForceTrend.com subscription.
GET https://ForceTrend.com/api/leaderboard.php
The response is JSON and contains ranked instruments, score, directional UP and DOWN counts, and a ticker/kicker value when available.
Subscription and API key
API requests are available only for active subscribers. If the subscription on the account expires, API calls return an error until the subscription is renewed.
Where to find your API key
Log in, open your account from the user chip in the top navigation, then look for the API key panel. The same panel also shows a ready-to-copy leaderboard endpoint.
Keep it private
Treat your API key like a password. For production integrations, call the API from your server instead of exposing the key in public browser-side code.
Subscription required
The key identifies your account, and the API checks that the account has an active subscription before returning leaderboard data.
How to send your key
Send the key using one of the supported methods below. Header authentication is recommended for server-side integrations.
Recommended header
curl -H "X-API-Key: YOUR_API_KEY" "https://ForceTrend.com/api/leaderboard.php?hours=24&limit=25"
Bearer token
curl -H "Authorization: Bearer YOUR_API_KEY" "https://ForceTrend.com/api/leaderboard.php?source_filter=both"
Query parameter
curl "https://ForceTrend.com/api/leaderboard.php?api_key=YOUR_API_KEY&hours=24"
Optional query parameters
| Parameter | Values | Description |
|---|---|---|
hours |
Integer | Leaderboard lookback window in hours. If omitted, the site default is used. |
limit |
Integer | Maximum number of leaderboard rows to return. If omitted, the site default is used. |
source_filter |
both, json, direct |
Choose all signals, only assertion-based JSON signals, or only direct instrument signals. |
api_key or key |
Your API key | Alternative query-string authentication when headers are not practical. |
What data you receive
Successful requests return a JSON object with request metadata and a leaderboard array. Each row represents one ranked instrument.
| Field | Type | Meaning |
|---|---|---|
success |
Boolean | Whether the request succeeded. |
generated_at |
String | ISO 8601 timestamp for when the API response was generated. |
hours |
Integer | The lookback window used for the leaderboard calculation. |
source_filter |
String | The signal source filter used for the request. |
subscription_active |
Boolean | Confirms that the authenticated account has an active subscription. |
leaderboard[].Rank |
Integer | Instrument rank in the current leaderboard result. |
leaderboard[].Instrument |
String | The market instrument identified by the system. |
leaderboard[].Score |
Number | The calculated informational score for the instrument. |
leaderboard[].UP |
Integer | Number of upward AI-detected news signals in the selected window. |
leaderboard[].DOWN |
Integer | Number of downward AI-detected news signals in the selected window. |
leaderboard[].kicker |
String or null | Ticker, exchange symbol, or display shortcut when available. |
Example successful response
{
"success": true,
"generated_at": "2026-06-01T18:00:00+02:00",
"hours": 24,
"source_filter": "both",
"subscription_active": true,
"leaderboard": [
{
"Rank": 1,
"Instrument": "AAPL",
"Score": 82.45,
"UP": 12,
"DOWN": 3,
"kicker": "AAPL"
}
]
}
Common error responses
| Status | Error | When it happens |
|---|---|---|
401 |
Missing API key. or Invalid API key. |
No key was provided, or the key does not match an active user account. |
402 |
Active subscription required. |
The key is valid, but the account does not currently have an active subscription. |
403 |
User account is inactive. |
The user account attached to the key is disabled. |
405 |
Method not allowed. Use GET. |
The endpoint was called with an unsupported HTTP method. |
Use your account API key with an active subscription.
Open your account page to copy the key and endpoint, then call the leaderboard endpoint from your integration using one of the supported authentication methods.