Old Navy In-Store Availability API

Endpoint facts

Method

GET

API path

/oldnavy/product/availability

Auth

apiKey

Credits

3 credits/request

Platform

Old Navy

Response schema

#/definitions/oldnavy.availabilityResponseDoc

Overview

Checks per-size, in-store pickup stock status for one color (pid) at one or more physical stores. pid matches oldnavy-product's own color-level id. Give store location either directly with store_id (one or more comma-separated store ids, e.g. from a prior call to this endpoint or a value you already have) or with zip or both lat and lng, which resolves the nearest stores automatically. Select the storefront with the brand parameter (`on` for Old Navy, `gap` for Gap, `br` for Banana Republic, `at` for Athleta; defaults to `on`). Each returned store lists every offered size's stock status: `in_stock`, `out_of_stock`, or `low_stock`. 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

3 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

- Each store's `sizes` array lists every offered size's stock status: `IN_STOCK`, `OUT_OF_STOCK`, or `LOW_STOCK`. - `name`, `address`, `city`, `region`, `postal_code`, `phone`, and `distance_miles` are only populated when the store was resolved via `zip` or `lat`/`lng` -- a caller-supplied `store_id` has no accompanying store metadata from this source. - A `zip`/`lat`/`lng` search with no nearby stores returns a normal `200` with an empty `stores` array, not an error. - An unrecognized `pid` returns `404`. - An unrecognized `store_id` given directly (not resolved via `zip`/`lat`/`lng`) is not detectable as an error from this endpoint -- it returns every size as `OUT_OF_STOCK` rather than an error, a known upstream limitation. ```json { "code": 200, "msg": "OK", "data": { "pid": "907290012", "brand": "on", "style_id": "907290", "count": 1, "stores": [ { "store_id": "3444", "name": "TIMES SQUARE", "address": "1516 Broadway", "city": "New York", "region": "NY", "postal_code": "10036", "phone": "(646) 866-5935", "distance_miles": 0.77, "sizes": [ {"sku": "9072900120004", "fit": "REGULAR", "status": "IN_STOCK"}, {"sku": "9072900120000", "fit": "REGULAR", "status": "LOW_STOCK"} ] } ] } } ```

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