API Search action too many times

AI-generated summary

The user Bcat is facing an issue with the Discourse API search action, receiving a “You’ve performed this action too many times” error when making frequent requests from their website. They are using curl to query the search endpoint and are limited by IP-based rate limits. The community suggests using an administrator’s API username to bypass some rate limits riking and caching the search results locally to reduce API calls Stephen. Bcat confirms they are caching data for 24 hours and will try the admin API approach. Another user, Fenil, asks how Bcat resolved the issue, and Bcat explains their caching solution Bcat.

Error: You’ve performed this action too many times, please try again later.

I have a website that needs to call Search on my discourse to export topics. Currently ~ 100 requests at high time.
And I receive the error as above!
So how to increase this limit? Or by default if limited I need any solution to make API calls from other websites!

I am using: curl: http://meta.discourse.org/search/query.json?term=limit

Some current settings!

What are you trying to do? There may be a better way than making so many search calls.

I want to display the topic on the 2nd Website.
With domain2 / url /
With url will search on my discourse.

On header of CURL i had used Api-Key and Api-Username

{"posts":[],"users":[],"categories":[],"tags":[],"groups":[],"grouped_search_result":{"more_posts":null,"more_users":null,"more_categories":null,"term":null,"more_full_page_results":null,"can_create_topic":false,"error":"You\u2019ve performed this action too many times, please try again later.","post_ids":[],"user_ids":[],"category_ids":[],"tag_ids":[],"group_ids":[]}}

Seems limited by IP. Is there any way?

Use the Api-Username of an administrator to bypass some (!) of the ratelimits.

Are you caching the data locally?

The content of the topic after being saved is saved cache for “key” 24 hours and after 24 hours to retrieve it again at the same time many topics.

I will try. The current API user USER

@Bcat I am facing the same issue. How did you solve this issue?

I cache and write to the file and search for the file before recording and call a search in 24 hours