How to reduce strain on GraphQL indexer node by merging events requests

[codeuntilcold]

Discord user ID

No response

Describe your question in detail.

Is there a way to query for multiple event type's data using just one request?

Our application relies on the GraphQL indexer to index latest data to our own database for sorting, filtering, searching, etc. Specifically, the events method is used to get latest events from a given offset. We've been making a request for each event type and an offset. Although this is expensive, this is the only way that we've tested that works with this events method.

But about a week back seems like both the public RPC and indexer have been applied rate limit, which makes this way of doing things impossible.

What error, if any, are you getting?

Too Many Requests on indexer

What have you tried or looked at? Or how can we reproduce the error?

We've looked at using wildcards (e.g $packageId::$module::*) for querying events but it did not work.

We looked at Aptos Build to get the API key. Although it has a generous free tier, due to the nature of making a lot of requests, the estimated cost for our app is about $300-$500/month, and we cannot afford to delay the data freshness.

Which operating system are you using?

Linux (Ubuntu, Fedora, Windows WSL, etc.)

Which SDK or tool are you using? (if any)

TypeScript SDK

Describe your environment or tooling in detail

No response

[ying-w]

have you tried using where: {_or: {}} in graphql or using no code indexing