Get a Kickstarter campaign's detail API

Endpoint facts

Method

GET

API path

/kickstarter/project

Auth

apiKey

Credits

14 credits/request

Platform

Kickstarter

Response schema

#/definitions/kickstarter.projectResponseDoc

Overview

Returns one Kickstarter campaign's detail: funding snapshot (goal, pledged, percent funded, backers, state, dates), category, creator, cover photo, story text, risks & challenges, update/comment/FAQ counts, and reward/pledge tiers. creator and slug are the two path segments of the project URL, e.g. lookingglass and musubi for kickstarter.com/projects/lookingglass/musubi. Reward tiers are best-effort -- see the endpoint's documentation for when they may be omitted. 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

14 credits/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

Browser cluster behavior

Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.

For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.

You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.

Response behavior

Notable response behavior: - `story` and `risks_and_challenges` are the campaign's own text, server-rendered on both live and completed campaigns. - `updates_count`, `comments_count`, and `faq_count` come from the project page's own navigation tab labels, with `comments_count`/`backers_count`/`pledged`/`state` then refined by the campaign's own exact-match live-stats source when available. - `goal`, `percent_funded`, `staff_pick`, `spotlight`, `created_at`, `launched_at`, `deadline`, `usd_pledged`, and `converted_pledged_amount` are sourced from a `discover/advanced` search matched by an EXACT slug — a fuzzy lookup that can occasionally miss an older or lightly-indexed campaign, in which case those specific fields are left at their zero value rather than failing the whole request. - `reward_tiers` is sourced from kickstarter.com's own GraphQL response for the campaign's `/rewards` sub-page (each tier's `id`, `name`, `description`, `amount`, `currency`, `backers_count`, `estimated_delivery_on`, `image`, shipping fields, `remaining_quantity`, `limit`, `available`, `featured`, `items` (the reward's own contents), and `add_ons`). Best-effort: omitted from the response (not an error) when the capture misses or the campaign genuinely has no reward tiers (e.g. a completed or donation-only project) — the two are indistinguishable from this endpoint's point of view. - A nonexistent `creator`/`slug` pair returns `404`. A page Kickstarter blocks/challenges, or an unparseable response, returns a `503` upstream error. Example response: ```json { "code": 200, "msg": "OK", "data": { "id": 1114436418, "name": "musubi: the first consumer holographic frame", "slug": "musubi", "url": "https://www.kickstarter.com/projects/lookingglass/musubi", "blurb": "Turn any photo into a hologram.", "state": "successful", "goal": 50000, "pledged": 423762.5, "percent_funded": 847, "backers_count": 3009, "category": { "name": "Technology", "url": "https://www.kickstarter.com/discover/categories/technology" }, "creator": { "name": "Looking Glass", "url": "https://www.kickstarter.com/profile/lookingglass" }, "story": "Turn any photo or video into a hologram. No subscription required.", "risks_and_challenges": "The largest risk is manufacturing scale.", "updates_count": 12, "comments_count": 34, "faq_count": 8, "has_video": true, "reward_tiers": [ { "id": "UmV3YXJkLTExMDQ1MDc4", "name": "LAUNCH DAY SPECIAL", "description": "Save $50 off MSRP. Shipping charged separately after campaign ends.", "amount": 99, "currency": "USD", "backers_count": 998, "estimated_delivery_on": "2026-06-01", "shipping_enabled": true, "shipping_preference": "unrestricted", "shipping_summary": "Anywhere in the world", "items": [{ "name": "musubi holographic photo and video frame", "quantity": 1 }] } ] } } ```

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