Skip to main content

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​

  1. Read the catalog to see which services and order types are on sale, with prices.
  2. Call resolve with a DexScreener pair link. It checks the pair qualifies and returns the order types it can take.
  3. Call POST /trending/orders with one of those order types. The response carries the order and its payment details.
  4. Follow the order with GET /trending/orders/:orderId, or cancel it with cancel while it is unpaid.

Services​

serviceWhat it is
dex-trendingTrending placement for a pair. One order type per order, quantity is always 1.
reactionsReaction packages. Up to 8 order types per order, each with its own quantity, plus a speed.
other-servicesPromotion 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.

Endpoints​

Browse​

Orders​