All integrationsMarket Data

Wefunder

Read public crowdfunding offerings, company updates, pitches and regulatory disclosures on Wefunder.

actions
9
triggers
3

Triggers

Start a workflow when something happens in Wefunder.

  • New offeringStarts a workflow when new offering.
  • New company postStarts a workflow when new company post.
  • New company questionStarts a workflow when new company question.

Actions

Steps a workflow can run in Wefunder.

  • List public offeringsReturns the offerings shown on wefunder.com/explore. the curated set of companies that meet Wefunder's discoverability bar (a soft-confirmed traction threshold plus approval), **one offering per company**. An "offering" is a fundraise, addressed by its id (`ofr_...`). **Public view (`read:public`).** Reachable with either a server-side (client_credentials) token or a user access token. Private rounds (e.g. Reg D 506(b)) are never listed, and low-traction or unapproved compan
  • Get a public offeringRetrieves a single offering by its id (`ofr_...`). With `read:public`, a valid id for a non-public offering (e.g. a private Reg D 506(b) round) returns `404`. having an id does not make an offering publicly resolvable. With `read:explore` on a user access token, the offering resolves if *that user* may see it on wefunder.com (e.g. an accredited-only or invited round), and the response gains `publicly_visible` and `invested`.
  • Get a company's public Form C disclosuresThe Details tab of the company's Wefunder page as structured data. the company's own Form C disclosures, section for section: financial statements for the fiscal years on file, the page's ratios, the founder's current-position disclosure (cash on hand, monthly revenue / costs / burn), the financial-condition narrative, document links, risks, use of funds, directors and officers, 20%+ holders, capital structure, prior offerings, outstanding notes and debts, and related-party
  • Get a company's pitchThe Overview tab's pitch as structured data: the story as ordered blocks (`heading`, `paragraph`, `list`, `image`, `video`, `footnote`), plus the perk tiers of the round the page shows the viewer. Images and embedded videos keep their place in the document with an absolute URL, because founders publish perk tiers, stretch goals, timelines, and charts as pictures (typically with no alt text) and a plain-text rendering would drop them. What is parsed is what the page renders: t
  • List a company's postsThe company page's Posts tab as data: the published updates, notes, and spotlights the viewer may see, pinned first then newest, with a plain-text excerpt each. With `read:explore` the viewer is the authorizing user, so a follower or investor sees the community- and investors-only posts the site shows them; with `read:public` it is the anonymous view. Same query as the tab (`FeedItem.viewable_by`); investments, Q&A threads, and investor quotes belong to other tabs and are not
  • Get one company post in fullOne post with its full plain-text content, by the id the list returned. Same visibility as the list; a post the tab would not show this viewer is a 404.
  • List a company's investor questions and answersThe company page's Ask tab as data: the questions investors asked and the answers, as the tab lists them for this viewer (the same repository and visibility as the site). Like the tab, questions default to the current raise. those asked since it opened (`meta.questions_since`); `past_raises=true` includes every raise, which the site offers to any visitor because past-raise questions are public. `sort` is the tab's dropdown: `relevance` (default: highlighted, then answered, t
  • Search companies by nameThe wefunder.com search bar, companies only. Same Algolia request, same result ordering, and same page size as the site's top bar, so the results are what a visitor typing the same text would see, in that order. companies raising now and companies funded in the past, whether or not they appear on `/explore`. The order is the site's search order (match quality first, then the site's tie-breaks); nothing here recommends. Each result carries the company's `co_` id for `GET /com
  • Get a company pageThe company page behind an offering, as structured data. the "click a company" step after `/explore`. Addressed by the `co_...` id every offering carries in its top-level `company` field (a bare string). Keeps apart the three raised numbers the page shows and readers conflate: `current_raise.amount_raised` (this campaign's live rounds combined, on Wefunder), `past_rounds[]` (prior rounds the page lists, each tagged `source: wefunder` for rounds observed here or `reported` fo

Automate Wefunder with Lodol.

Connect Wefunder, then hand Lodol the job in Slack, Claude or ChatGPT.

We’re letting people in a few at a time.