/indiegogo/campaigns/search

POST /api/indiegogo/campaigns/search

Price: 5 credits

Search and discover Indiegogo crowdfunding campaigns with filters and sort

How to use it

Search and discover Indiegogo crowdfunding campaigns. Filter by keyword, catalog category, campaign status (upcoming, crowdfunding, late pledge, funded, preorder, store), backer benefits, numeric tag IDs, creator, and tabletop player counts; sort by newest, most funded, most popular, ending soon, most discussed and more. Each result carries funding progress, category, tags, and the campaigner.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• term string nullable — Free-text keyword to match campaigns
• sort integer — Sort order (default: 0; one of: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9)
• categories array nullable — Filter by one or more catalog categories (one of: "TechAndInnovation", "General", "Productivity", "TravelAndOutdoors", "Home", "EnergyAndGreenTech", "CameraGear", "HealthAndFitness", "Transportation", "PhonesAndAccessories", "FashionAndWearables", "FoodAndBeverages", "Audio", "Education", "CreativeWorks", "Film", "Comics", "Music", "WritingAndPublishing", "DanceAndTheater", "Art", "WebSeriesAndTVShows", "OtherCreations", "PodcastsBlogsAndVlogs", "Photography", "CommunityProjects", "Wellness", "Culture", "LocalBusinesses", "OtherCommunityProjects", "Environment", "HumanRights", "GamingCulture", "BoardAndCardGames", "VideoGames", "TTRPG", "Accessories", "Others")
• phases array nullable — Filter by campaign status (upcoming, crowdfunding, ...) (one of: "Upcoming", "Crowdfunding", "Preorder", "Funded", "LatePledge", "Store")
• benefits array nullable — Filter by backer benefits (one of: "StablePledge", "StretchPay")
• tags array nullable — Filter by one or more numeric project tag IDs
• creator_id integer nullable — Filter by a specific creator ID
• player_counts array nullable — Filter tabletop games by supported player counts (one of: "One", "Two", "Three", "FourAndMore")
• count integer required — Number of campaigns to return (min: 1; max: 10000)

Response

• @type string (default: "IndiegogoCampaignCard")
• id integer required
• name string required
• alias string nullable
• tagline string nullable
• url string nullable
• image string nullable
• platform string nullable
• category string nullable
• currency_symbol string nullable
• goal number nullable
• funds_raised number nullable
• percent_funded number nullable
• backer_count integer nullable
• follower_count integer nullable
• funded_in_seconds integer nullable
• installment_count integer nullable
• installment_min_payment number nullable
• phase string nullable
• campaign_start_at integer nullable
• campaign_end_at 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

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 — The entity was not found, or a precondition failed 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.