/kickstarter/projects/rewards

POST /api/kickstarter/projects/rewards

Price: 10 credits

Get the reward tiers (pledge levels) of a Kickstarter project by slug or URL

How to use it

Get all reward tiers (pledge levels) of a Kickstarter project by slug or URL. Each tier returns the pledge amount and currency, USD-converted amount, backer_count, limit and remaining quantity, estimated delivery date, shipping details, and included items.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• project string required — Project slug ('creator/project-name') or full project URL (examples: "elanlee/exploding-kittens"; minLength: 1)

Response

• @type string (default: "KickstarterReward")
• id integer nullable
• name string nullable
• description string nullable
• amount number nullable
• currency string nullable
• converted_amount number nullable
• converted_currency string nullable
• backer_count integer nullable
• limit integer nullable
• limit_per_backer integer nullable
• remaining_quantity integer nullable
• estimated_delivery_date string nullable
• is_available boolean nullable
• is_max_pledge boolean nullable
• reward_type string nullable
• shipping_preference string nullable
• shipping_summary string nullable
• starts_at integer nullable
• ends_at integer nullable
• items array (default: [])
  • @type string (default: "KickstarterRewardItem")
  • id integer nullable
  • name string required
  • quantity integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Project not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.