BlockPeer Trade API — Overview

The BlockPeer Trade API is a REST-based API suite for issuing and managing TradeTrust-compliant electronic trade documents, including electronic Bills of Lading (eBL) and electronic Promissory Notes (ePN).

These APIs are designed to be consumed directly by existing enterprise systems—such as TMS, bank trade finance platforms, ERPs, and commodity trading systems—without requiring in-house blockchain development or TradeTrust implementation.

🧩 Built on the TradeTrust framework (abstracted for enterprises)

BlockPeer Trade APIs are natively built on the TradeTrust framework, but TradeTrust complexity is fully abstracted behind standard REST APIs.

This means:

Documents are TradeTrust-compliant by default
Verification follows TradeTrust’s open verifier model
Control and transfer are enforced via TradeTrust token registries
Documents remain interoperable and non-proprietary

No blockchain SDKs, smart contracts, or TradeTrust libraries are required to integrate these APIs.

🎯 Objective of the Trade API

The primary objective of the BlockPeer Trade API is to:

Remove adoption barriers for electronic Bills of Lading and other electronic trade documents

Specifically, the API enables organizations to:

Adopt TradeTrust-based eBLs using their existing systems
Avoid building or maintaining blockchain infrastructure
Avoid hiring blockchain developers
Avoid vendor lock-in or proprietary document formats
Continue using familiar trade workflows and UIs

🧑‍💼 Who uses these APIs (Use cases)

1️⃣ Transportation Management Systems (TMS)

Use case

Issue eBLs directly from TMS
Transfer eBLs to consignees, banks, or agents
Track document status inside existing shipment workflows

Value

No change to TMS user experience
No blockchain logic in the TMS codebase
Faster document turnaround vs paper BLs

2️⃣ Banks & Trade Finance Platforms

Use case

Receive and verify eBLs during LC presentation
Validate issuer identity and document control
Transfer or endorse eBLs to financing parties

Value

No wallet management
No TradeTrust SDK implementation
Works with existing trade finance software
Enables email or API-based LC presentation with verifiable eBLs

3️⃣ ERP Systems (SAP, Oracle, Odoo, etc.)

Use case

Issue or receive electronic trade documents from ERP workflows
Link eBLs to invoices, purchase orders, and shipments
Maintain audit trails without storing private keys

Value

ERP remains the system of record
TradeTrust compliance handled externally
No blockchain operational overhead

4️⃣ Commodity Trading & Trade Operations Platforms

Use case

Manage eBL and ePN lifecycle from trading desks
Enable document transfers for cargo resale
Integrate with financing and settlement flows

Value

Faster cargo monetization
Reduced document risk
Seamless integration with trade finance workflows

5️⃣ Logistics, Freight Forwarders & NVOCCs

Use case

Issue and transfer eBLs for shipments
Coordinate document flows between shippers, consignees, and banks

Value

Reduced courier costs
Real-time document status
Interoperable eBLs across counterparties

🔄 How enterprises integrate (Adoption model)

Traditional approach

Hire Blockchain Development Team
Implement TradeTrust SDKs

Deploy smart contracts

Manage blockchain keys

Build verifier logic

With BlockPeer Trade API

Call REST APIs

Authenticate once

Issue & manage eBLs

Verify documents via API

Your system remains unchanged. BlockPeer handles the TradeTrust framework implementation.

🔐 Authentication & authorization

Session-based authentication
Standard REST headers (Authorization: Bearer <token>)
No private key handling by integrators

🛡 Why this matters for eBL adoption

✅ TradeTrust-compliant eBLs
✅ No blockchain development required
✅ No vendor lock-in
✅ Existing systems remain unchanged
✅ Faster time-to-production
✅ Bank- and regulator-friendly architecture

🧭 Next steps

Authenticate and obtain a session token
Issue a TradeTrust-compliant eBL
Transfer or endorse documents from your system
Verify documents using BlockPeer or any TradeTrust-compatible verifier