Developers

FundComb Data API

Use scoped FundComb Data API keys to read published investor profiles and transaction comps with source-aware rights metadata.

API access is currently a managed beta for active Data-plan workspaces. Billing is not yet a general self-service promise. If your signed-in workspace has the entitlement, create and revoke keys from Data API settings.

Authentication and scopes

Send the one-time secret as an HTTP Bearer token. FundComb stores only its SHA-256 hash. Keys may carry read:investors, read:comps, or both; a workspace may keep up to 10 active keys.

Authorization: Bearer YOUR_FUNDCOMB_API_KEY

Read endpoints

Endpoint	Scope	Parameters
GET /api/v1/investors	read:investors	`limit` (1–100), numeric `cursor`, optional text `q`
GET /api/v1/comps	read:comps	`limit` (1–100), numeric `cursor`, optional exact `sector`

curl -H "Authorization: Bearer $FUNDCOMB_API_KEY" \
  "https://fundcomb.com/api/v1/investors?limit=50&q=venture"

curl -H "Authorization: Bearer $FUNDCOMB_API_KEY" \
  "https://fundcomb.com/api/v1/comps?limit=50&sector=consumer"

Pagination

Responses return data and a numeric nextCursor. Pass that cursor on the next request. A null cursor means the current result set is exhausted.

Rights and provenance

Only published rows are returned. Exportable observations and transaction-party evidence retain source, confidence, attribution, and rights fields; review each response’s rightsPolicy.

Invalid, expired, unentitled, or under-scoped keys return an authentication error. Usage is recorded by day, endpoint, request count, row count, and error count so workspace owners can audit integrations and revoke keys immediately.