Organizations
An organization is your developer account. You create and manage it in the developer portal; there is no API endpoint for it.
What an organization owns
| Owned by the organization | Not owned by any organization |
|---|---|
| Applications, each with a sandbox and a live OAuth client | Companies, offerings, campaigns |
| Client secrets and their rotation | Investments and investors |
| Webhook endpoints (shared by every installation of an app) | Syndicates and their members |
| Team members and their portal roles | Users |
| Its sandbox realm |
The right-hand column is global. Your app reaches those records only through a user who authorized it or a company or syndicate that installed it. See the access model.
Organization types
| Type | Meaning |
|---|---|
platform | Wefunder itself and its own branded surfaces |
partner | Every organization created through the developer portal |
The type affects where offerings are discoverable, not what data an organization can access.
Getting an organization
Anyone who edits a company or manages a syndicate on Wefunder can open the portal and create one. Everyone else joins the API waitlist and is approved by Wefunder. Once approved, the person who creates the organization becomes its owner and can invite teammates.
One organization, several applications
An organization can own any number of applications, for example a web dashboard, a mobile client, and a sync service. Owning an app grants it nothing by itself. Each app's reach is the union of the users who authorized it and the companies and syndicates that installed it, capped by the scopes it declared.
Identifiers
Organizations carry an org_ external id and applications an app_ id. Neither appears in API responses today; you see them in the portal and in install links.