Gymshark API endpoint
Use Crawlora's Gymshark Pages API to extract supported public Gymshark 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.
/gymshark/pagesReturns normalized static pages from Gymshark (https://row.gymshark.com). The storefront URL is fixed server-side. 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 |
|---|---|---|---|---|---|
| page | integer | No | 1 | 1-based page, defaults to 1 | |
| limit | integer | No | 50 and supports up to 250 | Maximum static pages, defaults to 50 and supports up to 250 | |
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/gymshark/pages?page=1&limit=10" \ -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.
- Page content is cleaned text from Shopify `body_html`; raw HTML is not returned. - Valid empty page arrays return `200` with an empty `pages` array. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. - If the classic `/pages.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to enumerating page handles from the storefront's own `pages` sitemap. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, and each item only carries `handle`, `url`, and `updated_at` -- no `title`, `id`, or `content`. Call the single-page endpoint per handle for full content. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport). Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://row.gymshark.com", "source_url": "https://row.gymshark.com", "page": 1, "limit": 50, "pages": [ { "id": "54831906896", "handle": "example-page", "title": "Example Page", "url": "https://row.gymshark.com/pages/example-page", "content": "Example page content" } ] } } ```
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 |
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"store_url": "https://row.gymshark.com",
"source_url": "https://row.gymshark.com",
"page": 1,
"limit": 50,
"pages": [
{
"id": "54831906896",
"handle": "example-page",
"title": "Example Page",
"url": "https://row.gymshark.com/pages/example-page",
"content": "Example page content"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/shopifybrands.pagesResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | shopify.PagesResponse | No | ||||
| data.limit | integer | No | 50 | |||
| data.page | integer | No | 1 | |||
| data.pages | array | No | ||||
| data.pages[].content | string | No | ||||
| data.pages[].created_at | string | No | ||||
| data.pages[].handle | string | No | accessibility | |||
| data.pages[].id | string | No | 54831906896 | |||
| data.pages[].published_at | string | No | ||||
| data.pages[].title | string | No | Accessibility | |||
| data.pages[].updated_at | string | No | ||||
| data.pages[].url | string | No | https://www.allbirds.com/pages/accessibility | |||
| data.source_url | string | No | https://www.allbirds.com | |||
| data.store_url | string | No | https://www.allbirds.com | |||
| data.transport_mode | string | No | ssr_embedded | ssr_embedded | TransportMode is present only when the store required the embedded-SSR-JSON fallback transport. In this mode pages are discovered from the storefront's own pages sitemap rather than a listing API: each item only carries handle/url/updated_at (no title or content) — call GET /shopify/pages/{handle} per handle for full content. | |
| msg | string | No | OK |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/gymshark/pages?page=1&limit=10" \
-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