Trending
Order DexScreener trending, reaction packages and other promotion services for a token, on behalf of your end users. Prices are the ones the end user pays: their own discount is already applied.
How it works
- Read the
catalogto see which services and order types are on sale, with prices. - Call
resolvewith a DexScreener pair link. It checks the pair qualifies and returns the order types it can take. - Call
POST /trending/orderswith one of those order types. The response carries the order and its payment details. - Follow the order with
GET /trending/orders/:orderId, or cancel it withcancelwhile it is unpaid.
Services
service | What it is |
|---|---|
dex-trending | Trending placement for a pair. One order type per order, quantity is always 1. |
reactions | Reaction packages. Up to 8 order types per order, each with its own quantity, plus a speed. |
other-services | Promotion packages. Needs a provider from the catalog. |
Availability
Trending may be unavailable. While it is, every
/trending/* endpoint answers 503 with
{ "message": "Trending is not available" } — after authentication, so
a bad token still gets 401. If the service is temporarily
down, endpoints answer 503 with
{ "message": "Trending service unavailable, retry later" }; retry
with backoff.
Safe retries
POST /trending/orders accepts an optional
Idempotency-Key header. Send one so a retry after a timeout returns
the first response instead of creating a second paid order.