/indiegogo/campaigns

POST /api/indiegogo/campaigns

Price: 5 credits

Get Indiegogo crowdfunding campaign details by slug or URL

How to use it

Get full details of an Indiegogo crowdfunding campaign by slug or URL. Returns funding progress (goal, funds_raised, percent_funded, backer_count, currency), campaign timeline (start/end dates, phase), category and tags, the full project story, reward tiers (perks), stretch goals, and the campaigner (creator name, bio, location, legal entity).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• campaign string required — Campaign slug ('stardome-transparent-suite-pod') or campaign URL (examples: "stardome-transparent-suite-pod", "https://www.indiegogo.com/projects/stardome/stardome-transparent-suite-pod"; minLength: 1)

Response

• @type string (default: "IndiegogoCampaign")
• id integer required
• name string required
• alias string nullable
• tagline string nullable
• story string nullable
• risks string nullable
• refund_policy string nullable
• url string nullable
• image string nullable
• category string nullable
• currency string nullable
• currency_symbol string nullable
• goal number nullable
• funds_raised number nullable
• funds_raised_total number nullable
• percent_funded number nullable
• backer_count integer nullable
• total_backer_count integer nullable
• phase string nullable
• campaign_outcome string nullable
• campaign_start_at integer nullable
• campaign_end_at integer nullable
• funded_at integer nullable
• published_at integer nullable
• campaign_day integer nullable
• perk_count integer nullable
• tags array (default: [])
  • @type string (default: "IndiegogoTag")
  • id integer nullable
  • name string required
  • alias string nullable
• game_properties object nullable
  • @type string (default: "IndiegogoGameProperties")
  • min_age integer nullable
  • min_players integer nullable
  • max_players integer nullable
  • play_time integer nullable
• creator object nullable
  • @type string (default: "IndiegogoCreator")
  • id integer nullable
  • name string nullable
  • alias string nullable
  • image string nullable
  • profile_url string nullable
  • bio string nullable
  • location string nullable
  • legal_entity_name string nullable
  • legal_entity_type string nullable
  • created_at integer nullable
• perks array (default: [])
  • @type string (default: "IndiegogoPerk")
  • id integer nullable
  • name string required
  • description string nullable
  • price number nullable
  • retail_price number nullable
  • currency string nullable
  • is_discounted boolean nullable
  • is_digital boolean nullable
  • is_featured boolean nullable
  • is_most_popular boolean nullable
  • has_limited_stock boolean nullable
  • remaining_stock integer nullable
  • claimed_count integer nullable
  • estimated_delivery_at integer nullable
  • image string nullable
  • url string nullable
• stretch_goals array (default: [])
  • @type string (default: "IndiegogoStretchGoal")
  • id integer nullable
  • name string required
  • abstract string nullable
  • description string nullable
  • target_value number nullable
  • target_type string nullable
  • progress number nullable
  • is_unlocked boolean nullable
  • is_featured boolean nullable
  • unlocked_at integer nullable
  • image string 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 — Campaign 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.