The limit of queries per second depends on the nature of the requests, service, and request parameters (amount of results, amount of queries, etc.). The average QPS is about 20 (soft limit). However, Outscraper can scale according to your needs. Please contact the team in case you need higher QPS.

Evet. API, dizileri şu sayıya kadar göndererek gruplamayı destekler 25 sorgular (örn, query=text1&query=text2&query=text3). Birden fazla sorgunun tek bir istekte gönderilmesine ve ağ gecikme süresinden tasarruf edilmesine olanak tanır.

Şu adrese gidin API Kullanım Geçmişi sayfası son taleplerinizi görmek için.

Şuraya gidin profil sayfasıYeni bir anahtar oluşturmak için ->API belirteci.

Ortalama yanıt süresi 3-5 saniyedir. Ancak bu süre hizmet türüne (hız optimizasyonlu veya değil) ve istek başına sorgu sayısına (toplu iş seçeneği) bağlı olabilir.

There are a few key points you should follow to increase the throughput of the API.

1. Make sure you are using the latest versions of the API endpoints. For example, prefer using Places API V2  instead of Places API V1. In the case of using SDK the last version of API will be used by default (e.g. google_maps_search()).
2. Use batching to send up to 25 queries per one request (e.g., query=text1&query=text2&query=text3). It allows multiple queries to be sent in one request and save on network latency time.
3. Run requests in parallel. Check out this example.
4. Use a webhook to fetch results once it’s ready.

Some tasks can take time to extract the data. There are a few ways you can handle timeouts.

1. Use retries. Expect that some number of scraping requests might return an error or timeout. Usually, trying one more time solves the issue.
2. Use async requests. A good practice is to send async requests and start checking the results after the estimated execution time. Check out this Python implementation as an example.
   
3. Use a webhook to fetch results once it’s ready.