Papa John's Menu API

Endpoint facts

Method

GET

API path

/papajohns/menu

Auth

apiKey

Credits

1 credit/request

Platform

Papa John's

Response schema

#/definitions/papajohns.menuResponseDoc

Overview

Returns a Papa John's US or Canada restaurant's full menu with that restaurant's own prices. Prices are per restaurant, not national -- the same 14-inch pizza can differ by several dollars between two stores -- so pass a store_id from GET /papajohns/store or GET /papajohns/nearby. Omitting it returns the national default menu, flagged as national_default in the response. Each category is returned with its sections and product groups, and every orderable SKU carries its price, calories, serving size, slice count and image. Set include_options to also get each product group's customization axes: every size and crust it is sold in, and every preparation instruction (how much cheese, how well done) with its choices. This is the US and Canada menu -- for India use GET /papajohns/india/menu, and for Chile, Costa Rica, Guatemala, Panama, Portugal or Spain use GET /papajohns/intl/menu. 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

- `national_default` is `true` when no `store_id` was supplied, so a caller can always tell the fallback menu from a real restaurant's prices. - Each category contains sections, each section contains product groups, and each group contains the orderable SKUs with `price`, `calories`, `serving_label`, `slices` and an image. `price_from` on a group is its cheapest priced SKU. - A build-your-own SKU whose price depends entirely on the customer's choices reports `price` `0`; read the group's size and crust options instead. - Sections upstream hides, and groups whose SKUs carry no price, are omitted rather than returned looking free. - `available_topping_ids` are upstream's own numeric topping ids. This upstream publishes no names for them, so they are exposed as ids rather than invented labels; `max_toppings`, `max_same_topping` and `allow_half_toppings` give the rules that go with them. - An unknown `category` or a negative/non-numeric `store_id` returns a `400`; a `store_id` the upstream has no menu for returns a `404`. Example response: ```json {"code":200,"msg":"OK","data":{"store_id":5054,"national_default":false,"categories":[{"id":"pizza","name":"Pizza","sections":[{"id":"most_popular","name":"Most Popular","product_groups":[{"id":"cyo","title":"Create Your Own Pizza","description":"Build your own custom pizza and we'll handcraft it for you.","customizable":"full","price_from":14.99,"max_toppings":7,"max_same_topping":2,"allow_half_toppings":true,"products":[{"sku":"1-1-2-115","name":"10 Inch Original Pepperoni Pizza","title":"Small Original Crust - Pepperoni","size":"Small","price":14.99,"regular_price":14.99,"code":"PR10Q1","size_id":2,"crust_id":1,"calories":210,"serving_label":"/slice, 6 slices","slices":6}]}]}],"product_count":96}],"product_count":206,"source_url":"https://www.papajohns.com/api/trpc/menuCategory.getByStore?input={\"json\":{\"storeId\":5054}}","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