Use documented REST endpoints to retrieve active trading scenarios, whale alerts, signal history, supported assets and platform-status data in a structured machine-readable format.
GET https://api.wallstreethack.com/v1/signals/active Authorization: Bearer YOUR_API_KEY Accept: application/json { "status": "success", "data": [ { "signal_id": "wsh_sig_000241", "asset": "BTC-USDT", "direction": "long", "signal_status": "active" } ] }
The Wall Street Hack API provides programmatic access to structured trading-signal data. The API is intended for dashboards, notification systems, internal trading tools and approved automated integrations.
API responses provide informational market data and structured scenarios. They do not guarantee accuracy, profit or a specific trading result.
All private endpoints require an active API key. Pass the key in the Authorization header using the Bearer authentication scheme.
Authorization: Bearer YOUR_API_KEY Accept: application/json Content-Type: application/json
Keep credentials on the server side. Do not publish API keys in client-side JavaScript, public repositories, screenshots or browser source code.
All version-one requests use the following base URL. Endpoint paths are appended after the version prefix.
https://api.wallstreethack.com/v1
https://api.wallstreethack.com/v1
v1
/api-status/
Request limits depend on the approved API-access level. Limit headers may be returned with each response so clients can manage request volume.
X-RateLimit-Limit: 1000 X-RateLimit-Remaining: 984 X-RateLimit-Reset: 1785168000
| Header | Description | Example |
|---|---|---|
X-RateLimit-Limit |
Maximum requests available during the current window. | 1000 |
X-RateLimit-Remaining |
Requests remaining before the limit is reached. | 984 |
X-RateLimit-Reset |
Unix timestamp for the next limit reset. | 1785168000 |
The core endpoint set provides access to active signals, individual signal records, historical records, whale alerts, supported assets and API-service health.
/signals
Private
Returns a paginated collection of signal records matching the supplied filters.
curl --request GET \ "https://api.wallstreethack.com/v1/signals?status=active" \ --header "Authorization: Bearer YOUR_API_KEY"
/signals/{signal_id}
Private
Returns one complete signal object, including its current status and available analytical context.
curl --request GET \ "https://api.wallstreethack.com/v1/signals/wsh_sig_000241" \ --header "Authorization: Bearer YOUR_API_KEY"
/signals/active
Private
Returns signals currently marked as active or partially closed.
curl --request GET \ "https://api.wallstreethack.com/v1/signals/active" \ --header "Authorization: Bearer YOUR_API_KEY"
/signals/history
Private
Returns closed, expired and invalidated signal records for a defined time range.
curl --request GET \ "https://api.wallstreethack.com/v1/signals/history?limit=50" \ --header "Authorization: Bearer YOUR_API_KEY"
/whale-alerts
Private
Returns contextual alerts related to large-wallet flows, exchange transfers and monitored entity activity.
curl --request GET \ "https://api.wallstreethack.com/v1/whale-alerts?asset=BTC" \ --header "Authorization: Bearer YOUR_API_KEY"
/assets
Private
Returns assets and market pairs currently supported by the signal and alert system.
curl --request GET \ "https://api.wallstreethack.com/v1/assets" \ --header "Authorization: Bearer YOUR_API_KEY"
/status
Public status
Returns the current operational state of API services and major data components.
curl --request GET \ "https://api.wallstreethack.com/v1/status"
A signal object contains identification, market, direction, risk, status and timing data. Availability of individual fields depends on the user’s API-access level.
{
"signal_id": "wsh_sig_000241",
"asset": "BTC",
"market": "BTC-USDT",
"signal_type": "spot",
"direction": "long",
"signal_status": "active",
"entry_zone": {
"from": 118400,
"to": 119100
},
"invalidation_level": 116900,
"targets": [121500, 124000, 127800],
"risk_level": "medium",
"confidence_score": 82,
"published_at": "2026-07-27T08:30:00Z",
"expires_at": "2026-07-28T08:30:00Z"
}
| Field | Type | Required | Description |
|---|---|---|---|
signal_id |
string | Required | Unique identifier for the signal record. |
asset |
string | Required | Base asset associated with the signal. |
market |
string | Required | Trading pair or monitored market. |
signal_type |
string | Required | Spot, futures, whale alert, volatility alert or other supported type. |
direction |
string | Conditional | Long, short or neutral depending on signal type. |
entry_zone |
object | Conditional | Defined entry range for directional scenarios. |
invalidation_level |
number | Conditional | Price or condition that invalidates the scenario. |
targets |
array | Conditional | Potential management zones associated with the scenario. |
risk_level |
string | Required | Internal risk classification. |
confidence_score |
integer | Required | Internal score from 0 to 100. |
published_at |
datetime | Required | ISO 8601 publication timestamp. |
expires_at |
datetime | Conditional | Time after which the scenario should no longer be considered current. |
The signal-status field identifies the current lifecycle stage of a market scenario.
The required activation conditions have not yet occurred.
The scenario is active and being tracked.
Part of the scenario has completed while another part remains open.
The scenario has reached its planned conclusion.
The original invalidation condition has been reached.
Clients should not assume that a signal remains active indefinitely. Refresh records or subscribe to status-change webhooks.
List endpoints may support filtering by asset, direction, signal type, status and publication date.
GET /v1/signals ?asset=BTC &signal_type=spot &direction=long &status=active &limit=50 &cursor=next_page_cursor
| Parameter | Type | Description |
|---|---|---|
asset |
string | Filter records by base asset. |
signal_type |
string | Filter by supported signal category. |
direction |
string | Filter directional signals by long or short. |
status |
string | Filter by current lifecycle status. |
from |
datetime | Return records published after the supplied time. |
to |
datetime | Return records published before the supplied time. |
limit |
integer | Maximum number of records returned per page. |
cursor |
string | Cursor supplied by a previous paginated response. |
Approved API users may receive event notifications when a signal is published, activated, updated, closed or invalidated.
Provide an HTTPS destination capable of receiving POST requests.
Choose signal-created, status-updated, alert-created or service events.
Validate the webhook signature before accepting the event payload.
Respond with a successful HTTP status after processing the event.
{
"event_id": "evt_000891",
"event_type": "signal.status_updated",
"created_at": "2026-07-27T09:15:00Z",
"data": {
"signal_id": "wsh_sig_000241",
"previous_status": "active",
"current_status": "partially_closed"
}
}
Errors use standard HTTP status codes and include a structured error object with a code, message and request identifier.
{
"status": "error",
"error": {
"code": "invalid_api_key",
"message": "The supplied API key is not valid.",
"request_id": "req_9e7b31"
}
}
The request contains invalid parameters or malformed data.
The API key is missing, expired or invalid.
The credential does not include access to the requested resource.
The requested signal, alert or endpoint could not be found.
The request limit for the current window has been exceeded.
An unexpected API-side error prevented the request from completing.
Major versions are included in the request path. Breaking changes should be introduced through a new major version instead of silently changing an existing response contract.
/v1
Validate response fields and handle unknown optional fields without failing the entire integration.
API credentials provide access to private signal data. Protect them as sensitive production secrets.
Use encrypted environment variables or a dedicated secrets-management system.
Do not send credentials or webhook data over unencrypted connections.
Remove API keys, authorization headers and sensitive payloads from application logs.
Replace credentials after suspected exposure or according to internal policy.
Reject webhook requests that do not pass signature validation.
Provide API credentials only to systems and team members that require them.
Review the main requirements for authentication, access, rate limits and API-data use.
Request API credentials for an approved dashboard, alerting workflow or internal trading tool. Review the API Terms of Use before processing or storing private signal data.