RedCircle
DATA · DATA & ANALYTICS
Target product details, search, reviews, and in-store stock on their own key.
Connecting RedCircle in practice
RedCircle reads Target in real time, so when its parsers break it answers 503 with a message and a retry_after rather than returning partial data, and it does not charge for that request. Bulk work has to go through Collections, which cap at 15,000 requests each — or 100 when include_html=true — and whose Result Sets are downloadable for only 14 days.
Scopes that draw scrutiny
api_key (query parameter)The only credential, passed as ?api_key= on every call including /account, so it lands in any log that records URLs. It spends the account’s monthly request credits.
Rate limits
- Requests are metered as monthly credits against the plan; GET /account reports the number used in the current month and is not itself charged.
- 402 Payment Required when credits are exhausted or a payment has failed; 429 when a plan-level or endpoint-level rate limit is hit.
- Concurrently running Collections: 5 for Collections of up to 250 requests, 1 for Collections over 250 requests.
- Requests added per API call: 1,000, up to the 15,000 per Collection; 15,000 per bulk CSV upload.
Worth knowing
- Collections that have not been started for over 2 months are deleted automatically, and Result Sets expire 14 days after they are produced.
- Automatic pagination multiplies the count: with max_page=10 a Collection holds 1,500 requests rather than 15,000, and max_page itself caps at 100.
- Passing skip_on_incident makes a request fail cleanly during a parsing incident instead of returning data RedCircle considers unstable — the safer default for an unattended agent.
- Collections per account cap at 10,000, so a workflow that creates one Collection per job needs to delete as it goes.
Checked against Collection limits (2026-09-29), Response codes (2026-09-29), Getting started (2026-09-29), Account API (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put RedCircle behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.