List the companies you follow
GET/users/me/follows
The authenticated user's watchlist — the companies they follow on wefunder.com (the same
rows the site's Follow button writes), newest first. Each entry is in the search-result
shape (co_ id, name, tagline, URL, logo, raising, profile_available) plus
followed_at.
Accepts read:profile or write:follows. Both include read:profile:follows, the
follows list on its own, which is what this endpoint checks. A token holding only
write:follows can list its follows here but cannot read the profile (GET /users/me).
Which companies are listed depends on the grant, the same way the follow list on a user's public Wefunder profile does:
write:follows,read:mcp(or the retiredread:follows): the full list, every company the user follows. An app that follows and unfollows for the user, or the user's own AI assistant acting as them, sees what the user sees.read:profileorwrite:profilewithout one of those: the public list. A company that has asked not to be promoted (promotion_opt_infalse onGET /companies/{id}) is left out, exactly as it is left out of the profile's follow list for every visitor but the user. This holds for every user, admins included.
The filter is applied before paging, so it never shortens a page, and page_count counts
the rows returned.
Request
Responses
- 200
- 401
- 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.
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