Papa John's Poland Menu API

Endpoint facts

Method

GET

API path

/papajohns/poland/menu

Auth

apiKey

Credits

1 credit/request

Platform

Papa John's

Response schema

#/definitions/papajohns.storefrontMenuResponseDoc

Overview

Returns Papa John's **Poland** menu with prices in Polish zloty. Russia and Poland run one franchise platform of their own, separate from the six markets behind GET /papajohns/intl/menu and from Colombia, Peru and El Salvador, so each has its own endpoint. The catalog is national -- it does not vary by city -- and every product lists its priced variants with size, dough and any stuffed crust. Prices are zloty and are not comparable with any other market. 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 catalog is **national**. Every ordering URL on this platform is city-scoped, which reads like a per-city menu, but it is not: two cities return the same products at the same prices, so no city parameter is offered. - `product_count` and `variant_count` report what the response carries. A product is listed once, with every priced variant under `variants`. - `size` carries the market's own unit as published (`23 см`, `29 cm`). - `crust` is the dough, where the market publishes one. - `stuffed_crust` names a filling baked into the rim: `cheese`, `sausage` or `sausage_cheese`. Upstream marks a plain variant `none`; that is reported here as an absent field rather than the literal word. - A variant with no price is not orderable and is left out; a product whose variants are all unpriced is left out entirely. - A `category` matching no section returns a `404`, so an empty filter result is distinguishable from an empty menu. Example response: ```json {"code":200,"msg":"OK","data":{"market":"poland","currency":"PLN","categories":[{"id":"1","name":"Pizza","alias":"pizza","products":[{"id":"1588","name":"Italian Sausage","category":"Pizza","price_from":49.99,"currency":"PLN","variants":[{"size":"29 cm","crust":"tradycyjna","price":58.98,"currency":"PLN","available":true,"sku":"1588"},{"size":"34 cm","crust":"tradycyjna","price":67.98,"currency":"PLN","available":true,"sku":"1541"}]}],"product_count":23}],"product_count":84,"variant_count":292,"source_url":"https://papajohns.pl/warszawa","fetched_at":"2026-09-07T09: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