This endpoint is read-only and can be used by any Integrating System that needs to validate a document before accepting or processing it.

How this fits in the Trade flow

• Called by the Integrating System
• Can be used at any stage of the document lifecycle
• Does not require End User approval
• Does not modify document state
• Safe for verification, audit, and compliance checks

The document provided should be the TradeTrust-formatted file (e.g., .tt or JSON representation).

What is verified

This endpoint validates:

• Document integrity (no tampering)
• Issuer identity (via DNS + registry)
• Signature authenticity
• Current controller of the document
• Validity of the endorsement / transfer chain

What this endpoint does NOT do

• ❌ Does not require authentication or approval
• ❌ Does not change document ownership or state
• ❌ Does not require registry roles
• ❌ Does not incur network transaction fees

This endpoint is purely informational.

Common use cases

• Validating an eBL received from a counterparty
• Checking issuer authenticity before financing
• Confirming control before accepting a transfer
• Audit and compliance verification

Interoperability note

TradeTrust documents verified using this endpoint can also be independently verified using:

• TradeTrust-compatible verifiers
• Other TradeTrust-compliant platforms

Verification is not locked to BlockPeer.

File Upload Format (Base64 Data URI)

For endpoints that accept file inputs, files must be submitted as a Base64-encoded Data URI string in the document field.

Format
data:<mimeType>;name=<filename>;base64,<base64EncodedContent>

Example
json
{ "document": "data:application/octet-stream;name=BL-0xd7.tt;base64,ewogICJAY29udGV4dCI6IFsKICAgICJodHRwcz..." }

Summary

• Verifies TradeTrust-compliant electronic trade documents
• Read-only and approval-free
• Confirms integrity, issuer, and control
• Suitable for banks, carriers, traders, and auditors