Find Target stores near a location API

Endpoint facts

Method

GET

API path

/target/stores

Auth

apiKey

Credits

2 credits/request

Platform

Target

Response schema

#/definitions/target.storesResponseDoc

Overview

Returns Target's physical stores near a ZIP code, a free-text "city, state", or a "latitude,longitude" pair, including each store's store_id, status, distance, phone, address, service list, time zone, and two weeks of daily opening hours. Use the returned store_id values with the store_id parameter on target-search, target-category-products, target-filter-options, and target-product. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

2 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- `count`/`stores` cover every store Target's own locator returns for the location and radius. A `place` with no stores within `within` miles returns a valid `count: 0` empty result, not an error. - A `place` that does not resolve to any real location returns a 404, not an empty `stores` list. - Each store includes `store_id` (the value every other Target endpoint's `store_id` parameter expects), `status`, `distance_miles`, `phone`, address fields, `time_zone`, `services` (Target's own service/amenity labels for that store, e.g. `"Starbucks Cafe"`, `"Drive Up"`), and up to two weeks of daily `hours`. Example response: ```json {"code":200,"msg":"OK","data":{"place":"95014","count":1,"source_url":"https://redsky.target.com/redsky_aggregations/v1/web/nearby_stores_v1?include_capabilities=true&limit=20&place=95014&within=100","fetched_at":"2026-09-15T10:00:00Z","stores":[{"store_id":"323","name":"Cupertino De Anza Blvd","status":"Open","distance_miles":2.62,"phone":"408-725-2651","address_line1":"20745 Stevens Creek Blvd","city":"Cupertino","state":"CA","postal_code":"95014-2123","country":"US","time_zone":"PST","services":["Wine, Beer & Spirits Available","Drive Up","Shipt Delivery","Fresh Grocery","Starbucks Cafe"],"hours":[{"date":"2026-09-15","day_name":"Tuesday","is_open":true,"open_time":"07:00:00","close_time":"23:00:00"}]}]}} ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related