List a company's investor questions and answers
GET/companies/:id/questions
The 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, then most liked), recent, upvoted, unanswered. Text is plain.
Questions and answers carry their id (cmt_...); the integer key never leaves the API.
Answers are the founders' own words.
q searches question and answer text (Postgres full text: quoted phrases and -word work;
one- or two-word queries also prefix-match) and replaces the sort with match rank —
meta.sort is then search and each result's match says whether its question or an
answer matched. unanswered_by_team=true keeps only questions with no live answer from the
company's team (the founder's queue; the unanswered sort merely orders by whether anyone
replied).
Request
Responses
- 200
- 400
- 401
- 404
- 429
Successful response
sort is not one of the tab's options, or q is over 200 bytes.
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 company, or one the site does not show this viewer.
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