Papa John's Deals API

Endpoint facts

Method

GET

API path

/papajohns/deals

Auth

apiKey

Credits

1 credit/request

Platform

Papa John's

Response schema

#/definitions/papajohns.dealsResponseDoc

Overview

Returns the promotions a Papa John's US or Canada restaurant is currently running. Each offer carries its redemption code, title, description, offer price and — where the deal advertises a saving — the struck-through regular price, plus its artwork and deal-builder link. Pass a store_id from GET /papajohns/store or GET /papajohns/nearby: promotions are store-specific, and the national response is largely placeholders prompting the customer to choose a store, which are omitted here rather than returned as real offers. 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

- **Pass a `store_id`.** Promotions are store-specific. The national response is largely locked placeholders prompting the customer to choose a store; those carry no id or offer code and are omitted here rather than returned as real offers. `national_default` reports which mode you got. - `offer_code` is the code the deal is redeemed with, and `url` is its deal-builder link. - `regular_price` is the struck-through pre-offer price and is present only when the deal actually advertises a saving — a deal that does not is not given a fake one. - A deal whose price depends on what the customer builds reports `price` `0`. - An invalid `store_id` returns a `400`. Example response: ```json {"code":200,"msg":"OK","data":{"store_id":5054,"national_default":false,"deals":[{"id":"66262","offer_code":"EDNJX","title":"Ultimate Pepperoni Pizza","description":"A large original crust pizza loaded with pepperoni, a parmesan-romano blend, and pizza sauce.","price":12.99,"regular_price":23.49,"tag":"Featured Deal","image_url":"https://www.papajohns.com/static-assets/a/images/web/hero/2026/p9-2026-ultpepp-deal.jpg","url":"https://www.papajohns.com/order/dealbuilder?dealId=66262&offerCode=EDNJX"}],"count":16,"source_url":"https://www.papajohns.com/api/trpc/deals.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