How to avoid rate limit error ( /api/v1/users/{id:.+} )

"Our App team is currently initiating a batch search query that involves querying approximately 30,000 users in a single operation, utilizing the /api/v1/users/{id:.+} endpoint.

Has anyone encountered a similar scenario from a functional perspective? If so, what recommendations or best practices would you suggest for handling this situation effectively?"