POST /trending/resolve
Check a pair or token and list the order types it can take, before ordering. Nothing is created and nothing is charged.
The pair is looked up on DexScreener and must qualify for the service. The same check runs again when you create the order.
Use case
Validate what the user pasted and show only the packages that apply to it, with their quantity bounds.
Headers
| Header | Required | Description |
|---|---|---|
Authorization | yes | Bearer <accessToken> |
x-user-id | yes | End-user id, 1–256 chars [A-Za-z0-9_-]. |
Content-Type | yes | application/json |
Body
| Field | Type | Required | Description |
|---|---|---|---|
service | string | yes | reactions, dex-trending or other-services. |
provider | string | for other-services | A provider name from the catalog. |
link | string | one of link / tokenAddress | DexScreener pair link, https://dexscreener.com/<chain>/<pair>. Max 300 chars. |
tokenAddress | string | one of link / tokenAddress | Only for other-services providers that are token-based. Max 64 chars. Base58 defaults to Solana; an 0x token must be known to DexScreener. |
Response 200
{
"target": {
"chain": "solana",
"family": "…",
"pairAddress": "…",
"tokenAddress": "…",
"tokenName": "…",
"tokenSymbol": "…"
},
"orderTypes": [ { "id": "…", "minQuantity": 1, "maxQuantity": 1 } ],
"speeds": [ { "value": "normal" } ]
}
| Field | Description |
|---|---|
target | The pair or token the order would apply to. |
orderTypes | Order types available for this target. Each id is a valid orderTypeId. reactions entries carry minQuantity / maxQuantity. |
speeds | reactions only. Allowed values for speed. |
orderTypes entries also include the catalog fields (price and so on)
for the same user; see catalog.
Errors
| Status | Meaning |
|---|---|
400 | Validation failed (service, provider, or neither link nor tokenAddress), link is not a DexScreener pair link, pair not found, the service is not sold for that chain, or the pair does not meet the requirements. |
401 / 403 | Token missing, invalid, expired or revoked / API inactive. |
429 | Per-client rate limit hit. |
503 | Trending disabled or unavailable. |
When a pair fails the requirements, the 400 body adds structured
detail:
{
"message": "The pair does not meet the trending requirements",
"issues": [ "…" ],
"tokenInfo": { "…": "…" }
}
issues lists what to fix; tokenInfo (present for dex-trending)
describes the token-info state on DexScreener.
Example
curl -X POST "$BASE_URL/trending/resolve" \
-H "Authorization: Bearer $ACCESS" \
-H "x-user-id: $USER_ID" \
-H "Content-Type: application/json" \
-d '{ "service": "dex-trending", "link": "https://dexscreener.com/solana/<pair>" }'