WaveBL

WaveBL is an Israeli digital trade platform, headquartered in Kfar Saba and founded out of the ZIM shipping group, that moves original electronic bills of lading (eBLs) and the trade documents around them between carriers, freight forwarders, cargo owners, customs brokers and banks. Its blockchain-backed, peer-to-peer network issues, endorses, transfers, amends and surrenders title documents without a central repository, and is sold as the WaveBL Digital Document Hub, electronic Master and House Bills of Lading, WaveBL for Customs and a trade finance module that presents structured documents to banks. It is used by MSC, ZIM, Hapag-Lloyd, ONE, PIL, Evergreen and Leschaco among others, is approved by the International Group of P&I Clubs, and has implemented the DCSA Standard Annex for eBL Platform Interoperability so eBLs can cross to other platforms. WaveBL runs a real API programme — it states publicly that its platform complies with the DCSA OpenAPI specification for Issuance and the DCSA eBL Surrender Response API — but it operates no developer portal, publishes no API reference, base URL or machine-readable specification, and its only public API article lived on a Zendesk help centre that has since been decommissioned.

WaveBL publishes 1 API on the APIs.io network. Tagged areas include Electronic Bill of Lading, Digital Trade, Trade Documents, Trade Finance, and Ocean Freight.

WaveBL’s developer surface includes engineering blog, support, signup flow, pricing, authentication, and 12 more developer resources.

31.8/100 thin Agent 13/100 agent aware Full breakdown ↓
scored 2026-09-04 · rubric v0.18.3
1 APIs
Electronic Bill of LadingDigital TradeTrade DocumentsTrade FinanceOcean FreightShippingLogisticsSupply ChainMaritimeCustomsBlockchainFreight ForwardingBankingDocument Exchange

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-04 · rubric v0.18.3
Regulatory Posture applies to this provider. Its tags matched the Banking & Open Finance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/wavebl: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

WaveBL Certificate of Authenticity API

Undocumented HTTPS API behind WaveBL's public Certificate of Authenticity tool — the free service at coa.wavebl.com that lets any party verify that a bill of lading or trade doc...

Pricing Plans 1

Published pricing tiers and plan structures.

Wavebl Plans Pricing

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Wavebl Rate Limits

0 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Wavebl Authentication

0 schemes

SECURITY

Wavebl Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: wavebl
name: WaveBL
description: WaveBL is an Israeli digital trade platform, headquartered in Kfar Saba and founded out of the ZIM shipping group,
  that moves original electronic bills of lading (eBLs) and the trade documents around them between carriers, freight forwarders,
  cargo owners, customs brokers and banks. Its blockchain-backed, peer-to-peer network issues, endorses, transfers, amends
  and surrenders title documents without a central repository, and is sold as the WaveBL Digital Document Hub, electronic
  Master and House Bills of Lading, WaveBL for Customs and a trade finance module that presents structured documents to banks.
  It is used by MSC, ZIM, Hapag-Lloyd, ONE, PIL, Evergreen and Leschaco among others, is approved by the International Group
  of P&I Clubs, and has implemented the DCSA Standard Annex for eBL Platform Interoperability so eBLs can cross to other platforms.
  WaveBL runs a real API programme — it states publicly that its platform complies with the DCSA OpenAPI specification for
  Issuance and the DCSA eBL Surrender Response API — but it operates no developer portal, publishes no API reference, base
  URL or machine-readable specification, and its only public API article lived on a Zendesk help centre that has since been
  decommissioned.
type: Index
image: https://wavebl.com/wp-content/uploads/2024/05/Logo.svg
url: https://raw.githubusercontent.com/api-evangelist/wavebl/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-09-04'
modified: '2026-09-04'
tags:
- Electronic Bill of Lading
- Digital Trade
- Trade Documents
- Trade Finance
- Ocean Freight
- Shipping
- Logistics
- Supply Chain
- Maritime
- Customs
- Blockchain
- Freight Forwarding
- Banking
- Document Exchange
apis:
- aid: wavebl:wavebl-certificate-of-authenticity-api
  name: WaveBL Certificate of Authenticity API
  description: 'Undocumented HTTPS API behind WaveBL''s public Certificate of Authenticity tool — the free service at coa.wavebl.com
    that lets any party verify that a bill of lading or trade document was issued and transferred on the WaveBL network. Its
    existence, base path and two operations are established from WaveBL''s own production build: the Angular bundle served
    at coa.wavebl.com constructs an HTTP client with baseURL "coadocuments" and calls the relative paths "search" and "verify".
    The surface is an AWS API Gateway fronted by CloudFront — an anonymous GET or OPTIONS to either path returns HTTP 403
    {"message":"Missing Authentication Token"} with x-amzn-errortype MissingAuthenticationTokenException and an x-amz-apigw-id
    header, which is the API Gateway answer for a method not defined on that resource, so only the POST methods the app itself
    uses are exposed. WaveBL publishes no reference, no OpenAPI and no authentication documentation for it, so no parameters,
    schemas, error shapes or auth scheme are recorded here. Listed as a measured, undocumented surface.'
  humanURL: https://coa.wavebl.com/
  baseURL: https://coa.wavebl.com/coadocuments
  image: https://wavebl.com/wp-content/uploads/2024/05/Logo.svg
  tags:
  - Electronic Bill of Lading
  - Document Exchange
  - Digital Trade
  properties:
  - type: Website
    url: https://coa.wavebl.com/
  x-access: undocumented
  x-evidence:
    discovered: '2026-09-04'
    method: probed
    source: https://coa.wavebl.com/main.e6cb0d051b98470c.js
    probes:
    - url: https://coa.wavebl.com/
      status: 200
    - url: https://coa.wavebl.com/coadocuments/search
      status: 403
    - url: https://coa.wavebl.com/coadocuments/verify
      status: 403
    - url: https://coa.wavebl.com/coadocuments
      status: 403
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/wavebl-domain-security.yml
- type: Website
  url: https://wavebl.com/
- type: Blog
  url: https://wavebl.com/blog/
- type: Support
  url: https://wsupport.wavebl.com/
- type: SignUp
  url: https://register.wavebl.com/wavebl/?trustedOrganizationCode=Generic
- type: Pricing
  url: https://wavebl.com/pricing-page/
- type: TermsOfService
  url: https://wavebl.com/terms-and-conditions/
- type: PrivacyPolicy
  url: https://wavebl.com/privacy-policy/
- type: Compliance
  url: https://wavebl.com/wave-bl-achieves-iso-27001-and-27017-compliance-certification/
- type: Conformance
  url: conformance/wavebl-conformance.yml
- type: Authentication
  url: authentication/wavebl-authentication.yml
- type: WellKnown
  url: well-known/wavebl-well-known.yml
- type: Packages
  url: packages/wavebl-packages.yml
- type: Plans
  url: plans/wavebl-plans-pricing.yml
- type: RateLimits
  url: rate-limits/wavebl-rate-limits.yml
- type: Lifecycle
  url: lifecycle/wavebl-lifecycle.yml
- type: LLMsTxt
  url: llms/wavebl-llms.txt
x-enrichment:
  date: '2026-09-04'
  status: minimal
  artifacts_added: 11
  pass: local-v3
x-coverage:
  state: gated
  reason: customer-only-docs
  detail: WaveBL's only public API documentation was a single help-centre article stating that its platform complies with
    the DCSA eBL Issuance and Surrender Response APIs; that Zendesk help centre has been decommissioned and support.wavebl.com
    now fails the TLS handshake outright, while its replacement — the Salesforce Experience Cloud community at wsupport.wavebl.com
    — serves an article sitemap that 404s and answers 401 on every non-public path, so integration material is now reachable
    only by signed-in customers and partners.
  evidence:
  - url: https://support.wavebl.com/hc/en-us/articles/18817090320029-DCSA
    status: 0
  - url: https://wsupport.wavebl.com/s/sitemap-topicarticle-1.xml
    status: 404
  - url: https://wsupport.wavebl.com/.well-known/api-catalog
    status: 401
  - url: https://docs.wavebl.com/openapi.json
    status: 403
  - url: https://wavebl.com/llms.txt
    status: 404
  - url: https://coa.wavebl.com/coadocuments/search
    status: 403
  - url: https://developer.wavebl.com/
    status: 0
  checked: '2026-09-04'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/wavebl"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/wavebl/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/wavebl/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.