/snapshot/spaces/search

POST /api/snapshot/spaces/search

Price: 1 credit

Search and list Snapshot governance spaces (DAOs) by keyword, network and category

How to use it

Search and list Snapshot governance spaces (DAOs), ranked by activity. Provide a keyword to match a space name or id, and optionally filter by network chain id and category (defi, social, protocol, gaming, grant, etc.). Each space includes its name, description, network, follower/proposal/vote counts, active proposals, voting configuration, strategies, treasuries, and verification status.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of spaces to return (min: 1)
• search string nullable — Keyword to match against space name or id (examples: "uniswap", "ens")
• network string nullable — Filter by network chain id (examples: "1", "137", "42161")
• category string nullable — Filter by space category (one of: "protocol", "social", "investment", "grant", "service", "media", "creator", "collector", "ai-agent", "gaming", "wallet", "music", "layer2", "defai", "defi", "rwa", "depin", "meme")

Response

• @type string (default: "SnapshotSpace")
• id string required
• name string nullable
• description string nullable
• network string nullable
• symbol string nullable
• image string nullable
• cover string nullable
• domain string nullable
• website_url string nullable
• terms_url string nullable
• twitter string nullable
• github string nullable
• farcaster string nullable
• coingecko string nullable
• email string nullable
• guidelines string nullable
• template string nullable
• members array (default: [])
• admins array (default: [])
• moderators array (default: [])
• categories array (default: [])
• follower_count integer nullable
• proposal_count integer nullable
• vote_count integer nullable
• active_proposal_count integer nullable
• rank integer nullable
• follower_count_7d integer nullable
• proposal_count_1d integer nullable
• proposal_count_7d integer nullable
• proposal_count_30d integer nullable
• vote_count_7d integer nullable
• min_score number nullable
• only_members boolean nullable
• is_verified boolean nullable
• is_flagged boolean nullable
• is_hibernated boolean nullable
• is_turbo boolean nullable
• is_private boolean nullable
• created_at integer nullable
• voting object nullable
  • @type string (default: "SnapshotSpaceVoting")
  • delay integer nullable
  • period integer nullable
  • type string nullable
  • quorum number nullable
  • quorum_type string nullable
  • blind boolean nullable
  • privacy string nullable
  • aliased boolean nullable
  • hide_abstain boolean nullable
• strategies array (default: [])
  • @type string (default: "SnapshotStrategyRef")
  • name string required
  • network string nullable
  • params object nullable
• validation object nullable
  • @type string (default: "SnapshotSpaceValidation")
  • name string required
  • params object nullable
• vote_validation object nullable
  • @type string (default: "SnapshotSpaceValidation")
  • name string required
  • params object nullable
• treasuries array (default: [])
  • @type string (default: "SnapshotTreasury")
  • name string nullable
  • address string nullable
  • network string nullable
• parent object nullable
  • @type string (default: "SnapshotSpaceRef")
  • id string required
  • name string nullable
  • image string nullable
  • network string nullable
• children array (default: [])
  • @type string (default: "SnapshotSpaceRef")
  • id string required
  • name string nullable
  • image string nullable
  • network 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 — 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.