TradeVowConnectRequest API access
Family C/v1/transactions

Transaction APIs

Create and manage the canonical Transaction 360 record that anchors parties, requirements, evidence, execution, finance and settlement.

Designed for: Originators, trade platforms, buyers, sellers and authorised execution partners

MethodEndpoint
POST
/v1/transactions

Register a transaction from an opportunity, purchase order, contract or partner platform.

GET
/v1/transactions

List only transactions visible to the authenticated partner.

GET
/v1/transactions/{transaction_id}

Return the partner-safe Transaction 360 projection.

PATCH
/v1/transactions/{transaction_id}

Update permitted facts with ETag / If-Match concurrency.

POST
/v1/transactions/{transaction_id}/activate

Request deterministic validation and activation.

POST
/v1/transactions/{transaction_id}/parties

Assign an organisation to a transaction role.

POST
/v1/transactions/{transaction_id}/requirements

Create a transaction or corridor requirement.

GET
/v1/transactions/{transaction_id}/timeline

Read the permission-filtered event timeline.

GET
/v1/transactions/{transaction_id}/actions

Read open partner actions and exceptions.

GET
/v1/transactions/{transaction_id}/institutional-review

Read a granted transaction-level view of evidence, readiness, review history and snapshot integrity.

Institutional decision support

See how transaction evidence becomes ready for institutional review.

Explore the UK–Tunisia demonstration to see the transaction, supporting evidence, finance-readiness position and review history in one connected view.

View the institutional transaction

Postman example

Create a partner-originated transaction

POST {{base_url}}/v1/transactions
X-TradeVow-API-Key: {{api_key}}
Content-Type: application/json
Idempotency-Key: {{$guid}}
X-Correlation-ID: {{$guid}}

Domain rules

  • Idempotency-Key is required for creation and commands.
  • Submitted facts remain distinct from derived lifecycle/readiness state.
  • Material updates require optimistic concurrency.
  • Every party role must resolve to a permitted organisation relationship.

Related events

transaction.createdtransaction.activatedtransaction.amendedtransaction.party_joinedtransaction.completed