Skip to main content
GET
/
api
/
developers
/
signals
/
{signalId}
Get a trade signal by signalId
curl --request GET \
  --url https://mcp.echozero.app/api/developers/signals/{signalId} \
  --header 'Authorization: Bearer <token>'
{
  "success": true,
  "data": {
    "id": "<string>",
    "signalId": "<string>",
    "developerAgentId": "<string>",
    "developerId": "<string>",
    "signal": {
      "action": "<string>",
      "tokenAddress": "<string>",
      "amount": 123,
      "tokenName": "<string>",
      "tokenSymbol": "<string>",
      "urgency": "<string>",
      "metadata": {},
      "reasoning": "<string>",
      "context": {},
      "confidence": 0.5,
      "executionPlan": {}
    },
    "livePriceSeeded": true,
    "status": "<string>",
    "webhookDelivered": true,
    "createdAt": "2023-11-07T05:31:56Z",
    "subscriberId": "<string>",
    "validationResult": {
      "passed": true,
      "validatedAt": "2023-11-07T05:31:56Z",
      "reason": "<string>"
    },
    "executionResult": {
      "success": true,
      "txHash": "<string>",
      "executedAmountUsd": 123,
      "errorMessage": "<string>",
      "executedAt": "2023-11-07T05:31:56Z"
    },
    "webhookDeliveredAt": "2023-11-07T05:31:56Z"
  }
}

Authorizations

​
Authorization
string
header
required

User JWT access token issued by POST /api/auth/verify or POST /api/auth/social/verify. Routes that accept both auth modes declare api-key and bearer-jwt security schemes.

Headers

​
x-signature
string

HMAC-SHA256 signature: HMAC-SHA256(secretKey, timestamp + METHOD + path + body). Optional -- when omitted, HMAC verification is skipped.

​
x-timestamp
string

Request timestamp in epoch milliseconds. Required when x-signature is provided. Rejected if drift exceeds 5 minutes.

Path Parameters

​
signalId
string
required

Response

Trade signal record.

​
success
boolean
required
Example:

true

​
data
object
required

Endpoint-specific payload