Skip to main content

Overview

A transaction record provides source-dependent event, target, participant and disclosed-amount context.

Field groups

  • Transaction context
  • Participants

Field reference

SOURCE_DEPENDENT describes availability; access is a separate product/rights boundary. Null means unknown, not false or zero.

Transaction type

Field ID: transaction.transaction_type. Group: Transaction context. Recorded investment/deal or exit category. Evidence / dates: Use only the source or event date actually recorded; record modification is not verification. Limitation: Do not infer a transaction stage or completion from a label alone.

Transaction date

Field ID: transaction.transaction_date. Group: Transaction context. The recorded investment, acquisition or exit event date. Evidence / dates: Use only the source or event date actually recorded; record modification is not verification. Limitation: Preserve available precision. A source publication date is not automatically the deal date.

Company or target

Field ID: transaction.target. Group: Transaction context. The company associated with the transaction record. Evidence / dates: Use only the source or event date actually recorded; record modification is not verification. Limitation: Related firms remain separate; no identity merge follows from a shared name.

Disclosed amount

Field ID: transaction.amount. Group: Transaction context. Recorded transaction amount where disclosed. Evidence / dates: Use only the source or event date actually recorded; record modification is not verification. Limitation: Native stated units; not currency-normalized valuation, complete financing terms or an audited enterprise value. Missing means unknown, not zero.

Amount currency

Field ID: transaction.currency. Group: Transaction context. Recorded currency associated with that amount. Evidence / dates: Use only the source or event date actually recorded; record modification is not verification. Limitation: Unknown currency remains null; no implied FX conversion.

Recorded participants

Field ID: transaction.participants. Group: Participants. Recorded investing organizations and their transaction roles. Evidence / dates: Use only the source or event date actually recorded; record modification is not verification. Limitation: An investing firm is not automatically an acquirer, seller or owner. Exit buyer identity is not universally exposed.

Relevant deal people

Field ID: transaction.people. Group: Participants. People associated with an investing organization or a recorded deal role. Evidence / dates: Use only the source or event date actually recorded; record modification is not verification. Limitation: A deal lead is not automatically an employee of the target company.

Relationships to other entities

A transaction can connect a target company, investing organization and relevant deal person. Preserve the recorded participant role. Do not relabel an investor as buyer, seller or controlling owner without supporting evidence. Related fund attribution is not universal.

Read transaction context

Fictional request brief, entities, sources, values and dates. This is a documentation example, not a live HTTP response or customer result. Missing dates remain null.
Current availability: Reviewed bounded request. Execution: Manual / scoped. Automated invocation: Not currently available. API endpoint: None. MCP execution: None.
A research brief for human scope review, not an API payload.

Evidence / dates

Supporting evidence attaches to a specific field. Missing publication, capture, observation and verification dates remain unknown. Subscription views do not expose every source URL or date. Read evidence and date semantics.

What may be unknown

Missing amount or currency remains unknown, not zero or USD. No FX-normalized valuation, complete financing terms or transaction execution is implied. Check currency and units against the source. This reference does not normalize financial-statement values or promise currency-comparable valuations.

Access & rights

Access scope: FULL_MARKET. Field descriptions are public; premium records remain permissioned. A task purchases the agreed bounded result, not database access, unrestricted API queries, contacts export or graph redistribution. Sources and unknowns accompany results. Purchaser authorization, scope acceptance, agreement and payment are required before manual fulfillment; no automated external task service is offered.