Handle retries, limits, and partial results

Recover from search errors while keeping retries and request usage predictable.

  • 阅读约 8 分钟
  • Scraper API
Handle search errors and retries

Overview

Validation, authentication, quota, and pre-admission capacity failures do not consume a request. A successful search uses one request unit, even if it returns no businesses. Terminal failed or canceled searches release their reservation. Partial successes use one request. An HTTP timeout may leave the original search processing with a request reserved; its final outcome determines whether it is charged. Test-key responses are simulated and free.

Usage

Check error.code and retryable. Honor Retry-After. Retry a timeout with the identical body and Idempotency-Key to avoid duplicate work or charges. Stop on validation, authentication, or quota failures. Each successful response contains up to 20 businesses; unavailable fields must not be invented.

See the Search API documentation for the current contract.

继续阅读

迈出下一步

搜索商户数据

每次 API 请求最多获取 20 家商户。