Discussions

Ask a Question
Back to all

Clarification on Real-Time API Rate Limits and Best Practices for High Volume Use

Hi everyone,

I'm currently integrating the GoPlus Token Security API into a dApp that processes a relatively high volume of token addresses in real time (especially during user trading activity). I've reviewed the docs, but I wanted to get some clarification on two points:

  1. What are the current rate limits for the real-time API endpoints (specifically /token_security/{chain_id})?
    The documentation mentions general usage limits, but I couldn't find exact numbers or throttling behavior for bursts of requests.

  2. What’s the recommended best practice for handling larger batches of addresses (e.g., 50+ tokens) without hitting rate limits or being blocked?
    Should we implement request queuing with a certain delay, or is there a batch endpoint that's more suitable for this kind of use case?

Bonus question: Is there any roadmap or plan to offer higher rate limits or enterprise-tier access for apps that need to scale beyond the default limits?

Would love to hear how others are managing this in production, or if the GoPlus team could provide some insights or updates.

Thanks in advance!

ragdoll hit