JimmyJohns API endpoint
Use Crawlora's Jimmy John's Sitemap API to extract supported public JimmyJohns data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/jimmy-johns/sitemapReturns one page of Jimmy John's sitemap-declared store index -- 9,700+ URLs at time of writing. Jimmy John's publishes three page variants per store (sandwiches, delivery, catering) and all three appear in the sitemap, so each entry carries a kind and the store number they share; filter with the kind parameter to enumerate one variant per restaurant. `sandwiches` is the canonical variant. A page past the end returns an empty list rather than an error, so a caller can walk to exhaustion. 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.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| shard | integer | No | Sitemap shard index (default 0) | ||
| page | integer | No | 1-based page within the shard (default 1) | ||
| page_size | integer | No | Entries per page, 1-500 (default 100) | ||
| kind | string | No | Filter by page variant. One of sandwiches, delivery, catering. Default all. Allowed values: sandwiches, delivery, catering | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/jimmy-johns/sitemap?page=1&kind=sandwiches" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"shard": 0,
"shard_count": 1,
"entries": [
{
"url": "https://locations.jimmyjohns.com/in/columbus/sandwiches-1414.html",
"path": "in/columbus/sandwiches-1414.html",
"kind": "sandwiches",
"store_number": "1414"
}
],
"count": 1,
"total_in_shard": 2817,
"page": 1,
"total_pages": 29,
"source_url": "https://locations.jimmyjohns.com/sitemap1.xml",
"fetched_at": "2026-08-31T17:30:00Z"
}
}Request schema
No body schema
Response schema
#/definitions/jimmyjohns.sitemapResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | Code is the HTTP status code or a custom code used to indicate the result of the request @example 200 | |||
| data | jimmyjohns.SitemapResponse | No | ||||
| data.count | integer | No | 100 | |||
| data.entries | array | No | ||||
| data.entries[].kind | string | No | sandwiches | Kind distinguishes the three page variants Jimmy John's publishes per store: sandwiches, delivery and catering. All three describe the same restaurant; `sandwiches` is the canonical one. | ||
| data.entries[].path | string | No | in/columbus/sandwiches-1414.html | |||
| data.entries[].store_number | string | No | 1414 | StoreNumber is the trailing id shared by all three variants. | ||
| data.entries[].url | string | No | ||||
| data.fetched_at | string | No | ||||
| data.page | integer | No | 1 | |||
| data.shard | integer | No | 0 | |||
| data.shard_count | integer | No | 1 | |||
| data.source_url | string | No | ||||
| data.total_in_shard | integer | No | 9789 | |||
| data.total_pages | integer | No | 98 | |||
| msg | unknown | No | Msg is the message that describes the result of the request @example "Request successful" |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/jimmy-johns/sitemap?page=1&kind=sandwiches" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms