Papa John's International Stores API

Endpoint facts

Method

GET

API path

/papajohns/intl/stores

Auth

apiKey

Credits

1 credit/request

Platform

Papa John's

Response schema

#/definitions/papajohns.intlStoresResponseDoc

Overview

Returns Papa John's restaurants in one of six international markets: Chile, Costa Rica, Guatemala, Panama, Portugal, and Spain -- either every restaurant near a coordinate, or one known restaurant looked up by id. Each restaurant carries its address, coordinates, phone, per-weekday opening hours split by fulfillment channel, accepted payment methods, delivery zones with their minimum-order and free-delivery thresholds, and live delivery/pickup open flags. Restaurants come back ranked by distance with no radius limit, five at a time by default; page and limit walk the rest, and the response reports total_count, the market's whole restaurant total. The returned id is what GET /papajohns/intl/menu prices against, and menu_id is what GET /papajohns/intl/ingredients reads. This covers those six markets only -- for India use GET /papajohns/india/stores, and for the US and Canada use GET /papajohns/directory, GET /papajohns/store, or GET /papajohns/nearby. 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

- The `id` on each restaurant is what [`/papajohns/intl/menu`](papajohns-intl-menu.md) prices against, and `menu_id` is what [`/papajohns/intl/ingredients`](papajohns-intl-ingredients.md) reads. Several restaurants usually share one `menu_id`. - `hours` has one entry per weekday per fulfillment channel, with `dispatch_method` naming the channel. Times are wall-clock in the restaurant's own local time; upstream's placeholder date is dropped. - `payment_methods` lists only the methods the restaurant actually accepts. - `delivery_zones` carries each tier's delivery fee and its minimum-order and free-delivery thresholds where the market publishes them. - A restaurant that is currently closed is still returned, with `delivery_open`/`pickup_open` false. - A coordinate search ranks the market's restaurants by distance and has no radius cut-off, so any coordinate returns the nearest ones rather than nothing. `count` is how many this response carries, and `page`, `total_pages` and `total_count` describe the rest of the ranking, so a first page is distinguishable from the whole of it. `total_count` is the market's entire restaurant total rather than a match count — for the same reason there is no radius cut-off — so it is the same for every coordinate in a market. - Raising `limit` returns more of the same ranking in one call rather than a different one: the first five of `limit=100` are the same five, in the same order, that the default returns. Pages carry no duplicates. - Asking for a `page` past the last one returns a `404` naming the last page, rather than an empty list. `page` below `1` is rejected as a `400`. - An empty restaurant list is never reported as a successful search. If the market has restaurants but none could be read, the request fails with a `503`; if the market carries no restaurants at all, it returns a `404`. - A `store_id` lookup ignores `fulfillment` and returns exactly one store, or a `404` if the market has no such restaurant. It has no search origin, so `latitude`, `longitude` and `fulfillment` are omitted from the response rather than reported as `0` — `0,0` is itself a real coordinate. - Supplying neither `store_id` nor a coordinate pair returns a `400`, as does an unknown `market` or `fulfillment` or an out-of-range coordinate. Example response: ```json {"code":200,"msg":"OK","data":{"market":"spain","fulfillment":"delivery","latitude":40.4168,"longitude":-3.7038,"stores":[{"id":9,"name":"Vallejo Nájera","menu_id":8,"address":"Paseo de Juan Antonio Vallejo - Nájera Botas, 25, 28005","city":"Madrid","region":"Madrid","phone":"+34910493017","latitude":40.401686,"longitude":-3.708348,"order_method":"both","delivery_open":true,"pickup_open":true,"delivery_wait_minutes":30,"pickup_wait_minutes":15,"future_orders":true,"external_delivery":true,"payment_methods":["apple_pay","bizum","cash","credit","direct_click_to_pay","google_pay","paypal"],"delivery_zones":[{"name":"La más fresca 6,99€","delivery_price":0}],"hours":[{"day":"monday","dispatch_method":"in_store","opens":"12:00:00","closes":"23:59:59"}]}],"count":5,"page":1,"total_pages":20,"total_count":97,"source_url":"https://api.papajohns.es/v1/stores?latitude=40.4168&longitude=-3.7038","fetched_at":"2026-09-06T09:00:00Z"}} ```

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