Papa John's International Product API

Endpoint facts

Method

GET

API path

/papajohns/intl/product

Auth

apiKey

Credits

1 credit/request

Platform

Papa John's

Response schema

#/definitions/papajohns.intlProductResponseDoc

Overview

Returns one product's own catalog record in one of six international markets: Chile, Costa Rica, Guatemala, Panama, Portugal, and Spain -- its description, imagery, dietary markers, and customization rules (whether toppings may be changed, how many extra ingredients are included free, and whether it can be used as one half of a half-and-half pizza). This record carries no price, because pricing is per restaurant: use GET /papajohns/intl/menu for prices. Product ids come from that same endpoint. 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

- `food_type` carries the dietary markers the market publishes, e.g. `vegetarian`. - `available_as_half` reports whether the product may be used as one half of a half-and-half pizza, and `cheese_changeable` whether its cheese may be modified. Both are stated positively here; upstream expresses them as negations. - `free_extras` is how many extra ingredients are included at no charge. - An unknown `product_id` returns a `404`; an unknown `market` or a non-numeric id returns a `400`. Example response: ```json {"code":200,"msg":"OK","data":{"market":"spain","id":8,"name":"Super Papa","category":"pizza","description":"Salsa de tomate natural, carne de cerdo especiada, pepperoni crujiente, york XL, pimiento verde fresco…","customizable":true,"available_as_half":true,"cheese_changeable":true,"image_url":"https://cdn.new.papajohns.es/pictures/pizzas/superpapa750x600.webp","slug":"super-papa","source_url":"https://api.papajohns.es/v1/pizzas/8","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