For AI agents: a documentation index is available at the root level at /llms.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
VISIBILITY-GATED READ: a row is returned only when BOTH the acquired and acquirer entities are publicly visible. An acquisition relationship that already exists (and is visible in the entity relationships resource) but returns 404 here means one counterpart entity is still hidden -- publish that entity (statusSitemapShow=true, statusHidePage=false) -- it is an unmet visibility prerequisite, not data-layer inconsistency or projection lag. A gated miss on an existing row returns 404 with title 'Acquisition Exists but a Counterpart Entity Is Not Public'. The acquired/acquirer roles in each row are always declared explicitly in the response via the acquiredEntity and acquirerEntity fields. The role query parameter only selects which side the path entity occupies in the WHERE clause: acquired (default) lists acquisitions where the path entity was bought; acquirer lists acquisitions where the path entity was the buyer; all lists or reads both sides in one response. Writes (POST/PUT/PATCH/DELETE) ignore role and always treat the path entity as acquired.
Path parameters
entityIdstringRequiredformat: "uuid"
Entity UUID whose acquisition rows are being read or written.
relationshipIdintegerRequired
Acquisition relationship row id (entity_relationship.id).
Query parameters
roleenumOptional
Selects which side the path entity occupies in the WHERE clause: acquired (default) lists rows where the path entity was bought; acquirer lists rows where the path entity was the buyer; all reads either side.
Allowed values:
Response headers
X-RateLimit-Limitinteger
Requests allowed per client IP in the current rate-limit window.
X-RateLimit-Remaininginteger
Requests left before the tightest applicable rate-limit bucket rejects.
X-RateLimit-Resetinteger
Seconds until the exhausted rate-limit bucket admits another request; 0 when none is exhausted.
Response
OK
acquiredEntityobject
Acquired company — read-only nested display projection of the scoped path entity.
acquirerEntityobject
Buyer — read-only nested display projection. Mutations identify the buyer only via the flat acquirerEntityId UUID, never a nested entity object.
evidenceobject
Booleans confirming each managed row written by the acquisition endpoint.
relationshipIdinteger
statusenum
Read stage, not transactionStatus: Acquisition before operating-status change; Acquired Subsidiary for active completed acquisitions; Acquired for terminal/folded/closed (including Closed (Acquihire)).
Allowed values:
amountlong or nullOptional
announcedAtdatetime or nullOptional
asOfdate or nullOptional
completedAtdatetime or nullOptional
createdAtdatetime or nullOptional
currencystring or nullOptional
dataConfidenceenum or nullOptional
Fundraise data confidence label
Allowed values:
fundraiseTransactionIdstring or nullOptionalformat: "uuid"
Canonical fundraise transaction UUID
investorJoinIdstring or nullOptionalformat: "uuid"
Type-safe identifier for fundraise investor joins
sourcestring or nullOptional
transactionStatusenum or nullOptional
Fundraise transaction status label
updatedAtdatetime or nullOptional
Errors
400
Bad Request Error
404
Not Found Error
406
Not Acceptable Error
422
Unprocessable Entity Error
429
Too Many Requests Error
500
Internal Server Error
503
Service Unavailable Error
VISIBILITY-GATED READ: a row is returned only when BOTH the acquired and acquirer entities are publicly visible. An acquisition relationship that already exists (and is visible in the entity relationships resource) but returns 404 here means one counterpart entity is still hidden — publish that entity (statusSitemapShow=true, statusHidePage=false) — it is an unmet visibility prerequisite, not data-layer inconsistency or projection lag. A gated miss on an existing row returns 404 with title ‘Acquisition Exists but a Counterpart Entity Is Not Public’. The acquired/acquirer roles in each row are always declared explicitly in the response via the acquiredEntity and acquirerEntity fields. The role query parameter only selects which side the path entity occupies in the WHERE clause: acquired (default) lists acquisitions where the path entity was bought; acquirer lists acquisitions where the path entity was the buyer; all lists or reads both sides in one response. Writes (POST/PUT/PATCH/DELETE) ignore role and always treat the path entity as acquired.
