CVS store locator API

Endpoint facts

Method

GET

API path

/cvs/store-locator

Auth

apiKey

Credits

1 credit/request

Platform

CVS

Response schema

#/definitions/cvs.storesResponseDoc

Overview

Returns nearby CVS store locations for a ZIP code or a latitude/longitude pair: address, phone, fax, distance, and retail store hours, plus a has_pharmacy existence flag and a list of general service indicators (e.g. photo, ATM, same-day delivery). Covers general store info only -- this does not return pharmacy hours, pharmacy phone, prescription data, or any patient-specific information. zip is a 5-digit US ZIP code; alternatively supply latitude and longitude together. CVS.com is only available from US/US-territory egress; a request from an unsupported region returns an upstream error rather than an empty result. 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

1 credit/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

- `store_hours` is the retail (front-of-store) weekly schedule only. - `has_pharmacy` is a plain existence flag (does this location have a pharmacy counter) — no pharmacy hours, pharmacy phone, or prescription data is returned. - `services` is the raw list of upstream service-indicator codes for the store (e.g. `PH_Photo_Ind`, `atmInd`, `RS_BOPIS_Ind`, `RS_SameDayDelivery_Ind`), passed through as-is rather than translated to friendly names. - CVS.com is only available from US/US-territory egress; a request from an unsupported region, or a page CVS blocks, returns a `503` upstream error rather than an empty or wrong result. - Missing both `zip` and `latitude`/`longitude`, or an invalid ZIP, returns a `400` invalid-parameter error before any upstream request is made. Example response: ```json {"code":200,"msg":"OK","data":{"total_count":5,"stores":[{"store_id":"9767","address_line1":"9045 WILSHIRE BOULEVARD","city":"BEVERLY HILLS","state":"CA","zip":"90211","phone":"3102735252","fax":"3102736289","latitude":34.06741,"longitude":-118.38934,"distance_miles":1.12,"time_zone":"PDT","store_hours":[{"weekday":"MON","open_time":"08:00 AM","close_time":"11:00 PM"}],"has_pharmacy":true,"services":["RX_Pharmacy_Ind","PH_Photo_Ind","atmInd","RS_BOPIS_Ind"]}]}} ```

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