/circle/creators

POST /api/circle/creators

Price: 5 credits

Get a Circle Discover creator by URL or slug: name, headline, bio, photo, social links, join date and the communities and courses they list.

How to use it

Profile the person behind Circle Discover communities and see everything they sell. The creator alias appears on circle/communities results.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• creator string required — Circle Discover creator URL or its slug (examples: "https://discover.circle.so/jason-breshears", "jason-breshears"; minLength: 1)

Response

• @type string (default: "CircleCreator")
• id string required
• alias string required
• name string required
• url string required
• headline string nullable
• bio string nullable
• image string nullable
• cover string nullable
• intro_video_url string nullable
• links array (default: [])
  • @type string (default: "CircleLink")
  • url string required
  • link_type string nullable
• status string nullable
• created_at integer nullable
• joined_at integer nullable
• listings array (default: [])
  • @type string (default: "CircleListing")
  • id string required
  • alias string required
  • name string required
  • url string required
  • short_description string nullable
  • price number nullable
  • price_label string nullable
  • image string nullable
  • video_url 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 — No Circle Discover creator at this slug 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.