/whop/communities

POST /api/whop/communities

Price: 20 credits

Get a Whop community by URL or route slug: pitch, verification, member count, rating and review count, logo, banner, social links, owner and creation date.

How to use it

Profile one Whop community from its whop.com URL. The returned id is what whop/communities/reviews and whop/communities/products take.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• community string required — Whop community URL or its route slug (examples: "https://whop.com/crystal-academy/", "crystal-academy"; minLength: 1)

Response

• @type string (default: "WhopCommunity")
• id string required
• alias string required
• name string required
• url string required
• description string nullable
• is_verified boolean nullable
• member_count integer nullable
• rating number nullable
• review_count integer nullable
• image string nullable
• banner string nullable
• owner object nullable
  • @type string (default: "WhopOwner")
  • id string required
  • alias string nullable
  • name string nullable
  • bio string nullable
  • image string nullable
  • city string nullable
  • country string nullable
• created_at integer nullable
• has_global_affiliates boolean nullable
• social_links array (default: [])
  • @type string (default: "WhopSocialLink")
  • platform string nullable
  • value string required

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 — No Whop community at this route 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.