Skip to Content
Welcome to the DuckyDux Docs! 🦆
Developer APIRate Limits

Rate Limits

The DuckyDux API implements tiered rate limiting to ensure fair usage and system stability. Limits are enforced per IP address and vary based on endpoint cost and usage patterns.

Rate Limit Headers

Every API response includes headers showing your current rate limit status:

RateLimit-Limit: 3
RateLimit-Remaining: 2
RateLimit-Reset: 1
X-RateLimit-Limit-Second: 3
X-RateLimit-Limit-Minute: 120
X-RateLimit-Remaining-Second: 2
X-RateLimit-Remaining-Minute: 119
HeaderDescription
RateLimit-LimitAllowed limit in current timeframe
RateLimit-RemainingRequests remaining
RateLimit-ResetSeconds until quota resets
Retry-AfterSeconds to wait (429 responses only)
X-RateLimit-Limit-SecondMax requests per second
X-RateLimit-Limit-MinuteMax requests per minute
X-RateLimit-Remaining-SecondRemaining this second
X-RateLimit-Remaining-MinuteRemaining this minute

Endpoint Limits

Swap quote and bundles submission (3/s, 120/min)

Operations requiring route finding and transaction simulation.

EndpointMethod
/v1/swap/quotePOST
/v1/bundles/quotePOST
/v1/bundles/sendPOST
/v1/bundles/sponsored/sendPOST

Assets balance/allowance and swap fees (5/s, 300/min)

Endpoints for balance checks and status polling.

EndpointMethod
/v1/assets/balanceGET
/v1/assets/allowanceGET
/v1/bundles/{bundle_id}GET
/v1/swap/feesGET
/v1/swap/fees/balanceGET
/v1/swap/fees/withdrawPOST

Search & Discovery (12/s, 720/min)

Token and pool search endpoints.

EndpointMethod
/v1/assets/searchGET
/v1/assets/search/topGET
/v1/pools/searchGET
/v1/pools/search/topGET
/v1/pools/{pool_address}GET
/v1/pools/{pool_address}/pricesGET
/v1/pools/by-token/{token_address}GET

Affiliates (20/s, 1200/min)

Affiliates related details.

EndpointMethod
/v1/affiliates/{address}/summaryGET
/v1/affiliates/{address}/earningsGET
/v1/affiliates/{address}/withdrawalsGET

Best Practices

  1. Check RateLimit-Remaining before making requests
  2. Use Retry-After header when receiving 429 responses
  3. Cache responses — Token metadata (hours), pool info (minutes), balances (seconds)
  4. Batch operations — Group swaps into bundles, query top lists instead of individual items
  5. Connection pooling — Reuse HTTP connections to reduce overhead

See the Error Handling Guide for complete implementation patterns.

Need Higher Limits?

Contact support@duckydux.com with:

  • Your use case and expected traffic patterns
  • Current IP address(es)
  • Expected requests per second/minute per endpoint

Cryptographic authentication (coming soon) will provide per-wallet rate limits.

Last updated on
ReferenceErrors