Join fundraise investor
Authentication
User bearer token: Supabase or Clerk session JWT, Clerk OAuth access token, or Clerk personal API key
Admin API key for system-to-system write operations
Query parameters
Owner-scoped resource UUID selector.
Owner-scoped resource slug selector.
Provider name for provider-native IDs or slugs.
Provider-native source ID.
Provider-native source slug.
Actor type; inferred as agent when agentChassis and agentModel are supplied, or as employee from an authenticated user JWT session.
Agent chassis token for agent-authored writes.
Agent model id for agent-authored writes.
Request
Investor-level attributed amount invested in the fundraise transaction currency. API and MCP request bodies use a JSON number such as 220000 or 123456.78; aventure-cli uses —amount-invested 220000 or —amount-invested 123456.78. Do not send currency signs, currency codes, comma grouping, quoted numeric strings, or abbreviations such as 220k or 0.22M. In PATCH application/merge-patch+json, amountInvested:null clears the value.
Exact announced timestamp used to disambiguate same-label rounds
Financial instrument/vehicle for this investor’s participation (e.g. SAFE, Preferred Stock, Convertible Note). Lets one round carry distinct vehicles per investor join. In PATCH application/merge-patch+json, omit to preserve the current value; financialInstrumentType:null clears it.
Existing investor entity identifier. The entity must already exist; create a referenced investor entity first with POST /v1/entities/detail.
Existing investor entity slug when investorEntityId is omitted. The entity must already exist; create it first with POST /v1/entities/detail.
Existing investor person identifier. The person must already exist; create a referenced investor person first with POST /v1/people/detail.
Existing investor person slug when investorPersonId is omitted. The person must already exist; create it first with POST /v1/people/detail.
Whether this investor led the round — the lead/anchor investor that set terms or made the primary commitment. Optional: defaults to false on create and replace when omitted; in PATCH application/merge-patch+json, omit to preserve the current value.
Fundraise round transaction id. The target entity id/slug is the entity that raised the round; for an Investment Firm investment, use the portfolio/fundraising company as target and identify the firm with investorEntityId or investorEntitySlug. When omitted, round lookup uses the target entity plus round/dateAnnounced.
Response
Investor identity, nested: investor.entityId for a firm/fund investor or investor.personId for an angel — exactly one is set. Read responses carry ids only, never flat investor* fields or names; resolve display names with GET /v1/entities/detail or GET /v1/people/detail.
Whether this investor is the lead investor for the round — the lead/anchor investor that set the round terms or made the primary commitment.
Investor-level attributed amount invested in the fundraise transaction currency. Serialized as a plain JSON number such as 220000 or 123456.78; no currency sign, currency code, comma grouping, or abbreviated amount text is valid.
Financial instrument/vehicle for this investor’s participation in the round (e.g. SAFE, Preferred Stock, Convertible Note). Distinct from the round-level financialInstrumentType: a single round can record different vehicles per investor join — e.g. an accelerator batch holding a capped SAFE and an uncapped-MFN SAFE as two joins.