Consider

Consider

Consider hosts portfolio job boards and talent networks for startup communities, VC firms, and accelerators. The Boards API exposes read-only access to companies, jobs, and aggregate board statistics tied to your Consider account.

Data Model

• Board — aggregate counts of portfolio companies and open jobs on your Consider board.
• Companies — portfolio startups keyed by website domain; each row includes name, funding stage, markets, logos, and open job count.
• Jobs — roles aggregated across the board or scoped to one company domain; include title, locations, seniority, skills, salary when available, and a public job URL.

Operational Order

1. Read board stats to understand scope (company and job counts).
2. List companies when you need portfolio coverage or want a domain for company-scoped job reads.
3. List jobs across the board or pass a company domain to scope results to one portfolio startup.

Scope and Limits

• This integration covers the Consider Boards API only: public job-board data for your board.
• Talent network members, candidate profiles, pipeline review, referrals, and ATS sync are not in the Boards API. Those workflows stay in Consider's product UI unless Consider exposes a partner API for your account.
• Pagination uses opaque offset tokens from response links; prefer links.next over hand-built URLs.
• Default page size is small; raise limit only when you need more rows (maximum 50 per request).

Gotchas

• Board-scoped keys — each API key is tied to one Consider customer board (for example a single VC or accelerator network). Results never span boards you do not administer.
• Domain identity — company-scoped reads require the company's website domain (example.com), not the Consider slug alone.
• Board vs company job filters — job_types, skills, and markets apply to board-wide job listings only. Company-scoped job reads (domain set) support date filters, descriptions, sort, and pagination per Consider's Domain Jobs API.
• Pagination — list responses include hasNext, offset, and links.next. Pass the returned offset string to fetch the next page; do not invent page numbers.
• Single company shape — one company by domain returns {data: {...}}; company lists return {data: [...]}.
• Descriptions — job descriptions are omitted unless you explicitly request them; they can be long HTML payloads.