This section provides a high-level overview of how Trade APIs are used to issue and manage TradeTrust-compliant electronic trade documents.
What the Trade APIs enable
Using BlockPeer Trade APIs, an Integrating System can:
- Issue electronic Bills of Lading (eBL)
- Issue electronic Promissory Notes (ePN)
- Verify TradeTrust-compliant documents
- Manage document lifecycle actions:
- Transfer
- Nominate / endorse
- Reject
- Return to issuer
All actions are executed in accordance with the TradeTrust framework.
How Trade APIs are used
BlockPeer Trade APIs
↓
IntegratingSystem
↓
EndUser (Authorized Signer)
- The Integrating System initiates trade actions
- The End User approves actions via redirect and passkeys
- BlockPeer orchestrates document lifecycle updates
Approval model (high level)
- Every eBL / ETR issuance or management action:
- Generates a redirect URL
- Requires End User approval
- Uses End User passkeys only
There are no alternative approval mechanisms.
What Trade APIs abstract
Integrating Systems do not need to:
- Implement the TradeTrust framework
- Deploy or manage smart contracts
- Build document verification logic
- Manage private keys or wallets
All TradeTrust-specific complexity is handled by BlockPeer.
What Trade APIs do NOT abstract
- Legal responsibility for approvals
- End User control over documents
- Network transaction fees (if applicable)
