RedCircle API
RedCircle API is the real-time Target product data API for accessing Target product catalog, reviews, and category data.
Verdict
Common use cases
- Monitor competitor pricing across regions daily
- Scrape product catalogs for inventory analysis
- Track availability changes for high-demand items
- Build datasets for market research reports
- Automate product data feeds to internal tools
Integration
- Vendor
- RedCircle API
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 32
- Composio slug
redcircle_api
Tools
- Add Zipcodes
Tool to add zipcodes to your RedCircle API account for geolocation targeting. Use when you need to localize product searches by specific postal codes. New zipcodes take approximately 2 minutes to become available after being added.
- Clear Collection Requests
Tool to remove all requests from a specified collection. Collections can only be cleared when not actively running. Use when you need to empty a collection of all its requests.
- Create Collection
Tool to create a new collection for running up to 15,000 requests on a schedule. Use when you need to organize and schedule batch requests with various scheduling patterns, priority levels, and notification methods.
- Create Destination
Tool to create a new destination for uploading Collection Result Sets to cloud storage. Use when you need to configure a storage destination for result sets with providers like S3, GCS, Azure, OSS, or S3-compatible storage.
- Create Requests
Tool to add up to 1,000 requests to an existing collection. Use when you need to populate a collection with product requests. Collections have a maximum of 15,000 requests (100 if include_html=true). Sequential calls required; parallel requ
- Delete Collectiondestructive
Tool to remove a collection from the system by ID. Use when you need to delete a collection that is not currently running.
- Delete Destinationdestructive
Tool to remove a destination from your RedCircle API account. Use when you need to permanently delete a specific destination by its ID.
- Delete Request from Collectiondestructive
Tool to remove an individual request from a collection. Use when you need to delete a specific request from a collection by providing both collection_id and request_id. Collections must not be running during deletion.
- Delete Requests In Bulkdestructive
Tool to delete multiple requests from a collection in bulk. Use when you need to remove multiple requests efficiently. Note: Requests can only be deleted when the collection is not running.
- Delete Zipcodesdestructive
Tool to remove zipcodes from your RedCircle API account. Use when you need to delete specific zipcode/domain pairs from your account.
- Get Account Information
Tool to retrieve account information, usage metrics, and platform status. Use when you need to check account credits, limits, plan details, or platform component status.
- Get Collection
Tool to retrieve complete information about a specific collection. Use when you need detailed collection metadata including status, schedule, and configuration.
- Get Requests CSV Links
Tool to retrieve CSV download links for all requests in a collection. Use when you need to export request data in CSV format. Each CSV file contains up to 1000 requests.
- Get Requests JSON Links
Tool to retrieve download links for all requests in a collection in JSON format. Use when you need to access request data from a specific collection. Returns paginated URLs for downloading request information.
- Get Result Set CSV
Tool to retrieve a result set in CSV format with optional field filtering. Use when you need to export processed results from a collection as CSV files. Supports field selection using dot notation for nested fields. Results maintain 14-day
- Get Result Set JSON
Tool to retrieve a result set in JSON format with download links. Use when you need to access processed results from a specific collection and result set. Returns detailed result information including download URLs for data files.
- Get Result Set JSON Lines
Tool to retrieve a result set in JSON Lines format with download links. Use when you need to access processed results as newline-delimited JSON files. JSON Lines format provides one valid JSON object per line, ideal for streaming and proces
- Get Target Product Data
Tool to retrieve Target data in real-time including search results, product information, reviews, or category listings. Use when you need to access Target.com product data such as searching for products, getting specific product details, re
- List Categories
Tool to retrieve all top-level (root) categories or filter results using optional parameters. Use when you need to browse the category hierarchy, search for specific categories, or retrieve category details. Parameters id, parent_id, and se
- List Collections
Tool to retrieve all collections configured on your RedCircle API account with filtering and pagination. Use when you need to browse collections, filter by status or search term, or manage collection metadata.
- List Destinations
Tool to retrieve all destinations configured on your RedCircle API account with pagination and filtering. Use when you need to browse or manage destination configurations. Returns 10 destinations per page.
- List Error Logs
Tool to list all error logs on your RedCircle API account. Use when you need to retrieve failed API request logs with error details. Results are paginated with 10 error logs per page. Supports filtering by search term and sorting by date or
- List Requests by Page
Tool to retrieve requests for a collection in paginated format. Use when you need to access collection requests with pagination support (max 1000 requests per page).
- List Result Sets
Tool to list all result sets for a collection. Use when you need to retrieve execution history and results for a specific collection. Note: result sets have 14-day retention.
- List Zipcodes
Tool to retrieve all zipcodes associated with your account with optional filtering. Use when you need to list zipcodes, optionally filtered by search term or domain. Supports pagination with max 10 results per page.
- Resend Webhook
Tool to resend a previously configured webhook POST request for a result set. Use when you need to debug webhook connectivity issues without re-executing the collection.
- Start Collection
Tool to initiate execution of a RedCircle API collection. Use when you need to start processing requests for a collection. Requires sufficient request credits and the collection must not be currently running.
- Stop All Collections
Tool to halt all currently active collections on your account. Use when you need to terminate all collection operations across your account. Collections in queued or running states are affected, resetting status to idle. Note: Queued collec
- Stop Collection
Tool to halt an active collection in queued or running state. Use when you need to stop a collection that is currently processing. Collections in queued status receive full credit refunds, while running collections are stopped without refun
- Update Collection
Tool to update an existing collection's configuration and settings. Use when you need to modify collection settings including name, schedule, priority, and destination assignments. Note: A collection can only be updated when it is not runni
- Update Destination
Tool to modify an existing destination configuration on your RedCircle API account. Use when you need to update destination settings such as name, credentials, storage paths, or enable/disable status. When enabling a previously disabled des
- Update Request
Tool to modify a request within a collection. Use only when the collection is not running. Updates request parameters like type, tcin, or other Target Product Data API fields.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations tab. 2. Click 'Add Integration' and select RedCircle API from the developer tools category. 3. Log into your RedCircle dashboard, navigate to API settings, and generate a new API key with read/write permissions. 4. Paste the API key into Switchy's auth field and click 'Connect'. 5. Switchy will verify the key and confirm the connection within a few seconds. 6. Open any Space and type '@RedCircle create a collection named test-run' to confirm the MCP responds. 7. If you need geolocation targeting, use the Add Zipcodes tool first — new zipcodes take about 2 minutes to activate. 8. To route results to cloud storage, create a destination with your S3, GCS, or Azure credentials before running collections.
What teammates see: by default, memories from RedCircle API are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Pricing Collection
@RedCircle create a collection named 'daily-pricing-check' with a schedule to run every morning at 8am UTCOpen in a Space →
Add Product Requests
@RedCircle add these 50 product URLs to collection ID 12345: [paste your list of URLs here]Open in a Space →
Configure Cloud Storage
@RedCircle create a destination for S3 with bucket name 'product-data-archive' and access key [your key]Open in a Space →
Target by Zipcode
@RedCircle add zipcodes 10001, 90210, 60601 to my account for geolocation targetingOpen in a Space →
Clear Old Requests
@RedCircle clear all requests from collection ID 12345 so I can load this week's targetsOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@RedCircle search for 'wireless headphones' on Amazon across 5 zipcodes we added last week and show me price ranges by region
I've queued a collection with 5 requests targeting the zipcodes you specified. Based on the current product data, wireless headphones range from $29.99 in postal code 10001 (New York) to $34.99 in 90210 (Los Angeles) for the top-ranked listing. Note that zipcodes added within the last 2 minutes may not yet be active for geolocation targeting. The collection will complete in approximately 30 seconds, and I can summarize pricing trends once all requests return.
This example shows geolocation-aware product search, a core RedCircle capability. Remember that newly added zipcodes require ~2 minutes to become active. Collections are limited to 15,000 requests, so large-scale geographic sweeps need batching. API key must have zipcode management permissions.
@RedCircle create a scheduled collection that checks our competitor's top 10 products every Monday at 9am and uploads results to our S3 bucket
I've created collection 'competitor-monitor-weekly' with 10 product requests and configured it to run every Monday at 09:00 UTC. The destination is set to your S3 bucket 's3://analytics-data/redcircle-results/' with the credentials you provided. The first run will execute next Monday. You can modify the schedule or pause the collection anytime. Note that collections with include_html=true are capped at 100 requests instead of 15,000.
This demonstrates RedCircle's automation layer: scheduled collections plus cloud storage integration. Collections can't be modified while running, so plan request lists carefully. The 15,000-request limit drops to 100 if you need full HTML responses. S3, GCS, Azure, and OSS are supported destination types.
@RedCircle pull the last result set from our 'holiday-pricing' collection and draft a summary of which products dropped below $50 in the past week
From the 'holiday-pricing' collection's most recent run (147 products checked), 23 items now fall under $50—up from 11 in the prior week. Notable drops include: 'Bluetooth Speaker XL' ($54.99 → $47.99), 'Smart Plug 4-Pack' ($59.99 → $49.99), and 'LED Desk Lamp' ($52.00 → $44.99). The steepest discount was 18% on the speaker. All results were uploaded to your configured GCS destination 4 hours ago. I can generate a full markdown report if you'd like to share this with the pricing team.
This example pairs RedCircle's batch data retrieval with AI synthesis. The MCP fetches structured result sets; the AI interprets trends and drafts summaries. Useful for competitive intelligence workflows. Be aware that result sets are only available after a collection completes—real-time product checks require individual API calls outside collections.
Use-case deep-dives
When RedCircle wins for competitive pricing teams tracking 5k+ SKUs
A 6-person e-commerce ops team needs to track competitor pricing across 8,000 SKUs daily. RedCircle's collection system handles 15,000 requests per scheduled run, so they batch their catalog into two collections that fire at 3am and 6am. The Create Requests tool loads SKUs in 1,000-item chunks, and the Create Destination tool pipes results straight to their S3 bucket for the pricing dashboard. This works because their catalog is stable—if you're adding hundreds of new products daily, the 2-minute zipcode indexing lag and the manual collection management become friction. If your SKU count stays under 10k and updates happen on a predictable schedule, RedCircle's batch-first design beats real-time APIs that charge per call.
How Add Zipcodes supports geo-targeted product research
A 3-person market research team is scoping a new product launch in 12 US metro areas. They use Add Zipcodes to register 47 postal codes across those regions, then schedule collections to pull product availability and pricing data localized to each zone. The 2-minute indexing delay is fine because they're planning weeks ahead, not reacting to live inventory. The catch: if your regions shift monthly or you need sub-zipcode precision, the manual zipcode management becomes a bottleneck. RedCircle shines when your geographic scope is defined upfront and stable for at least a quarter. For teams running one-off regional audits or testing 100+ zipcodes, the setup overhead outweighs the batch efficiency.
When collection scheduling beats ad-hoc scraping for compliance teams
A 4-person compliance team at a marketplace aggregator audits 3,000 seller listings weekly for policy violations. They create a collection with Create Collection, load listings via Create Requests, and schedule it to run every Monday at 8am. The Clear Collection Requests tool wipes the queue after each run, and they reload fresh listings from their database. This pattern works because compliance checks are periodic, not real-time, and the 15k request cap covers their audit scope. If your compliance window is tighter than daily or you need to react to flagged listings within hours, RedCircle's batch-only model won't keep pace. For weekly or monthly audits where you can tolerate a fixed schedule, the API key simplicity and built-in scheduling beat cobbling together cron jobs and rate-limit logic.
Frequently asked
What does the RedCircle API MCP do in Switchy?
It lets your team run scheduled product data collection at scale — up to 15,000 requests per collection — and route results to cloud storage. You can add zipcodes for geolocation targeting, manage request batches, and configure destinations like S3 or GCS. It's built for teams that need programmatic access to product data without writing scraper code.
Do I need admin access to connect RedCircle API?
You need an API key from your RedCircle account. Whoever connects it in Switchy should have permission to create collections, add requests, and configure destinations in RedCircle. The key lives in Switchy's encrypted vault; team members use the MCP without seeing the raw credential.
Can the MCP run collections while I'm editing them?
No. Collections must be stopped before you can clear requests, delete the collection, or remove individual requests. If a collection is running, those operations fail. You can create and add requests to a collection at any time, but destructive actions require the collection to be idle.
How does this compare to calling RedCircle's REST API directly?
The MCP wraps RedCircle's API so your AI agents can schedule collections, manage zipcodes, and configure storage destinations in natural language. If you're already scripting RedCircle calls, you won't gain much. If your team wants agents to orchestrate data pipelines without writing code, the MCP is faster.
Who on the team should connect the RedCircle MCP?
Whoever owns your RedCircle account and understands which collections and destinations matter. They'll connect it once in Switchy; after that, any team member can ask agents to create collections, add requests, or check zipcode coverage. The connector should know your cloud storage setup if you're using destinations.