BlockPeer Trade API — Getting Started

The BlockPeer Trade API enables developers to issue, verify, and manage electronic trade documents such as electronic Bills of Lading (eBL) and electronic Promissory Notes (ePN) using the TradeTrust framework.

BlockPeer is a TradeTrust-compatible platform, meaning:

• Documents follow TradeTrust data models and schemas
• Authenticity is verified using TradeTrust’s open verification model
• Documents are MLETR-aligned electronic transferable records
• Outputs can be verified independently using TradeTrust-compatible verifiers

🌐 What is TradeTrust (in this API context)

TradeTrust is an open framework developed to enable interoperable, verifiable electronic trade documents.

In BlockPeer:

• Each eBL / ePN is generated as a TradeTrust-compliant document
• Document control (issuer, holder, beneficiary) is governed via token registries
• Verification does not depend on BlockPeer — any TradeTrust verifier can validate the document
• Ownership and control changes are reflected through TradeTrust endorsement chains

BlockPeer extends TradeTrust with production-grade APIs, enterprise signing, and lifecycle orchestration — while preserving TradeTrust’s open, non-proprietary principles.

🔐 Step 1 — Authenticate and create an API session

To call the Trade API, you must first create a session token.

POST /auth/token

{
"email":"[email protected]"
}

Response

{
"token":"eyJhbGciOiJIUzI1NiIsInR5cCI6Ikp…"
}

Use this token in all subsequent requests:

Authorization: Bearer <token>

This session authorizes your organization to issue and act on TradeTrust-based documents using BlockPeer’s signing and registry infrastructure.

📄 Step 2 — Issue a TradeTrust-compliant eBL / ePN

You can now issue an electronic trade document that conforms to the TradeTrust standard.

POST /documents/ebl

(or /documents/epn)

{
"shipper":{ ...},
"consignee":{ ...},
"goods":{ ...}
}

Response

{
"documentId":"ebl_1234",
"status":"issued",
"tradetrust":{
"schema":"BillOfLading",
"version":"v2",
"network":"Polygon"
}
}

What happens under the hood

• A TradeTrust document is generated
• A token registry entry is created
• Issuer, holder, and beneficiary roles are recorded
• A verifiable TradeTrust .tt document can be rendered or shared

🔍 Step 3 — Verify a TradeTrust document

BlockPeer exposes verification endpoints that follow the TradeTrust verification flow.

POST /documents/verify

{
"document":{ ...}// TradeTrust JSON or .tt payload
}

Response

{
"verified":true,
"integrity":"valid",
"issuerIdentity":"verified",
"ownership":"current",
"framework":"TradeTrust"
}

Verification checks:

• Document integrity (hash & signature)

• Issuer identity (DID / DNS / identity proof)

• Endorsement chain validity

• Registry state on-chain

  All aligned with TradeTrust verification logic.

🔄 Step 4 — Manage TradeTrust lifecycle actions

TradeTrust defines control via endorsement and transfer, not duplication.

BlockPeer exposes lifecycle actions as APIs:

Each action:

• Updates the TradeTrust endorsement chain
• Updates the token registry
• Preserves singularity and control, as required under MLETR

🧠 Core Concepts (TradeTrust-aligned)

TradeTrust Document

A digitally signed electronic trade document whose authenticity and control can be independently verified.

Token Registry

A smart contract that represents control and role assignments for a TradeTrust document.

Endorsement Chain

A cryptographically verifiable history of transfers and endorsements, forming the legal chain of control.

Session Token

API authorization mechanism to request TradeTrust document actions.

🛠 Implementation Note (non-proprietary)

BlockPeer uses secure enterprise signing infrastructure to:

• Authorize TradeTrust document actions
• Submit registry transactions on supported blockchains
• Maintain compliance with TradeTrust’s open verifier model

BlockPeer does not introduce proprietary document formats or lock-in. TradeTrust documents generated via BlockPeer remain portable and verifiable across the ecosystem.

📘 Why this matters for banks & traders

• ✅ TradeTrust-based, not vendor-locked
• ✅ Legally aligned with MLETR / ETDA
• ✅ Independent verification
• ✅ API-first integration
• ✅ Wallet abstraction (no crypto UX burden)