Jupiter DCAs

tgm/jup-dca

post

List of Jupiter DCA orders with stats per vault.

Authorizations

Body

Responses

200

Successful response

application/json

400

Bad request

application/json

401

Authentication error

application/json

403

Forbidden - Subscription tier required

application/json

500

Internal server error

application/json

post

HTTPcURLJavaScriptPython

POST /api/beta/tgm/jup-dca HTTP/1.1
Host: api.nansen.ai
apiKey: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 178

{
  "parameters": {
    "chain": "solana",
    "tokenAddress": "2zMMhcVQEXDtdE6vsFS7S7D5oUodfJHE8vd1gnBouauv",
    "includeLabels": [],
    "excludeLabels": []
  },
  "pagination": {
    "page": 1,
    "recordsPerPage": 100
  }
}

[
  {
    "sinceTimestamp": "text",
    "lastTimestamp": "text",
    "traderAddress": "text",
    "creationHash": "text",
    "traderLabel": "text",
    "dcaVaultAddress": "text",
    "inputMintAddress": "text",
    "outputMintAddress": "text",
    "depositAmount": "text",
    "depositSpent": "text",
    "otherTokenRedeemed": "text",
    "closed": "text",
    "tokenInput": "text",
    "tokenOutput": "text",
    "depositUsdValue": "text"
  }
]

To optimize queries on the /tgm/jup-dca endpoint and avoid timeouts, use targeted filters rather than broad searches. Apply these strategies:

1. Set ‎⁠sinceTimestamp⁠ and ‎⁠lastTimestamp⁠ to limit results to a specific period.

2. Filter by ‎⁠traderAddress⁠ to focus on individual users.

3. Use thresholds like ‎⁠depositUsdValue⁠to target significant orders.

4. Filter by ‎⁠status⁠ to separate active from closed orders.

Combining these filters reduces data volume, speeds up queries, and improves reliability.

sinceTimestamp	Start date/time for results	“2025-06-01T00:00:00Z”
lastTimestamp	End date/time for results	“2025-06-27T00:00:00Z”
traderAddress	Filter by specific trader address	“YourTraderAddressHere”
depositUsdValue	Minimum USD value of deposit	1000
status	Order status (“Active” or “Closed”)	“Active”