Voyager Portal · AsyncAPI Specification

Voyager Portal Webhooks

Version

View Spec View on GitHub CompanyMaritimeShippingLogisticsDemurrageLaytimeVoyagesWorkflowsBulk CommoditiesAsyncAPIEvents

AsyncAPI Specification

voyager-portal-webhooks.yml Raw ↑
generated: '2026-07-21'
method: searched
source: https://gitlab.com/voyager-portal/voyager-public-api/-/wikis/Webhook
spec_type: Webhooks
description: Voyager Portal publishes outbound webhooks that push voyage, cargo,
  and SOF-validated events to a customer-supplied URL. No AsyncAPI document is published;
  this catalog captures the documented webhook surface.
configuration:
  setup: Webhooks are configured per company in the Voyager app under Settings >
    Companies > Integrations > Webhooks, with an event, a destination URL, and a
    shared token.
  verification_header:
    name: X-Voyager-Token
    description: Unique shared token sent in the header of every webhook request
      so receivers can verify the request is coming from Voyager.
events:
- name: Voyage
  trigger: Triggered every time a voyage is created or suspended.
  docs: https://gitlab.com/voyager-portal/voyager-public-api/-/wikis/Webhook/Voyage
  payload_highlights:
  - lastChange.action (add, etc.)
  - voyage id, code, company_id, laycan_from, laycan_to, vessel_id, status
  - schedules[] with port, ETA/ETD, and extra_data timeline fields
- name: Cargoes
  trigger: Triggered every time a cargo is added, updated, or deleted from a voyage;
    payloads differ slightly per action.
  docs: https://gitlab.com/voyager-portal/voyager-public-api/-/wikis/Webhook/Cargoes
  payload_highlights:
  - voyage {id, code, vessel}
  - lastChange {action, cargo {...}} with quantities, units, counterparties
  - allCargoes[] snapshot of the voyage's cargoes
- name: SOF Validated
  trigger: Triggered when a statement of facts (SOF) is validated, either by the
    SOF Validator or inside a voyage.
  docs: https://gitlab.com/voyager-portal/voyager-public-api/-/wikis/Webhook/SOF-Validated
  payload_highlights:
  - id, voyageCode, fileName, portName, vesselName
  - terminals[], berths[], cargoes[] with externalCargoRefId
  - integrationKey - client-supplied unique identifier for the SOF file, echoed
      back on validation

Work with this as data

Every AsyncAPI spec 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 asyncapi

4 MCP tools reach this
  • find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.
  • 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 AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/voyager-portal-webhooks"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?limit=25"

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

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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