/wefunder/companies/posts

POST /api/wefunder/companies/posts

Price: 5 credits

Get a Wefunder company's feed items (founder updates and investor buzz)

How to use it

Get a Wefunder (wefunder.com) company's feed items by slug, URL or numeric id. Choose the type: founder updates, investor buzz (investment announcements) or all. Each item carries the title, plain-text and HTML content, author, publish time and engagement counts (like_count, comment_count, read_count). Investor Q&A is available on the wefunder/companies profile (q_and_a field).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Company slug ('riserobotics'), company URL or numeric company id (examples: "riserobotics", "rejuvenatebio", "188422"; minLength: 1)
• post_type string — Feed item type to return (default: "updates"; one of: "updates", "investor_buzz", "all")
• count integer required — Number of feed items to return (min: 1)

Response

• @type string (default: "WefunderPost")
• id integer required
• document_title string nullable
• post_type string nullable
• visibility string nullable
• text string nullable
• content_html string nullable
• published_at integer nullable
• created_at integer nullable
• updated_at integer nullable
• like_count integer nullable
• comment_count integer nullable
• repost_count integer nullable
• read_count integer nullable
• url string nullable
• cover_image string nullable
• tags array (default: [])
• author object nullable
  • @type string (default: "WefunderPostAuthor")
  • id integer nullable
  • name string required
  • bio string nullable
  • image string nullable
  • profile_url string nullable
  • investor_profile_id integer nullable
  • is_wefunder_team boolean nullable
• subject object nullable
  • @type string (default: "WefunderPostSubject")
  • id integer nullable
  • name string nullable
  • alias string nullable
  • tagline string nullable
  • is_fund boolean 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 — Company 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.