Get a company page
GET/companies/:id
The 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 for founder-disclosed off-platform rounds), and
totals.profile_total_raised (the number on the page's ticker bar). Every figure comes
from the same policy the page uses, so the API never disagrees with the site.
Who has a page. Every company whose profile wefunder.com lists publicly — the same set
the site's search bar returns (published, not invite-only, searchable or with a live Form C;
accredited-only companies need an accredited viewer) — plus the /explore set. A funded
company, or one the viewer may see no round of, renders with raising: false and
current_raise: null; its history is in wefunder_rounds. Logged-in view
(read:explore) additionally covers the vault / syndicate-led companies the site shows an
accredited viewer, and the round described is the one the page would show that viewer. A
valid id for a company outside the viewer's set is a 404, never a partial payload.
A company's own token (minted from an install granted read:companies) reads the
page as the company's editors do on wefunder.com: the company always has a page, and
the round described is the one its founder sees, a private Reg D round included. It
is the company, not a person, so nothing about other companies' private rounds changes.
Request
Responses
- 200
- 401
- 404
- 429
Successful response
Authentication required or token is invalid/expired. This error occurs when:
- No Authorization header is provided
- The access token is invalid or malformed
- The access token has expired
- The access token has been revoked
To resolve: Obtain a new access token using the OAuth 2.0 flow.
Unknown id, or a company the viewer may not see.
Too many requests in a short time period. The API enforces rate limits to ensure fair usage and system stability. When you exceed the limit, you'll receive this error along with headers indicating when you can retry.
Check the X-RateLimit-Reset header to know when your limit will reset.
Consider implementing exponential backoff in your application.
Response Headers
Request limit per hour
Remaining requests
UTC timestamp when the limit resets