How this fits in the Trade flow

• Called by the Integrating System
• Used after:
  • Token Registry is deployed
  • DNS configuration is validated
  • Required registry roles (e.g., MINTER) are assigned
• Requires explicit End User approval
• Approval happens only via redirect URL and End User passkeys

Without End User approval, the eBL is not issued.

What happens next

1. The Integrating System redirects the End User to redirectUrl
2. The End User reviews eBL issuance details
3. The End User approves issuance using passkeys
4. The eBL is issued and recorded under the Token Registry
5. The Integrating System stores the issued eBL details for future management actions

Template note (important)

• This endpoint issues eBLs using a standard Bill of Lading template by default.
• If a carrier requires a carrier-specific BL format, please contact BlockPeer.
  • A one-time carrier-specific template setup is required.

Once the carrier template is enabled, the Integrating System can continue issuing eBLs via the same API flow.

Important notes

• Issuance requires End User approval via redirect + passkeys
• Network transaction fees apply (paid by the End User-controlled account)
• BlockPeer does not store the Integrating System’s customer records or eBL business context
• The Integrating System should persist:
  • registryAddress
  • eBL identifiers / references returned post-issuance (from follow-up/status endpoints, if applicable)

Next steps

➡️ Verification → Verify Digitally-Signed Trade Document

➡️ Document Lifecycle Management → Transfer / Endorse / Return actions

Summary

• Initiates TradeTrust-compliant eBL issuance
• Uses standard template by default
• Carrier-specific templates require one-time setup with BlockPeer
• Approval is mandatory via redirect URL + End User passkeys
• Integrating System remains the system of record

This API returns a redirect URL with sessionId to sign the transaction.
Use the GET endpoint /auth/session-response?sessionId=<sessionId> to retrieve the session result.
The response will include an object under the key wrappedDocument, which contains the content of the .tt file.

If using MCP, enter shipperDomain, holderAddress, and beneficiaryAddress explicitly.