Terminal49 Schedules

Access and versioning

• No authentication is currently required on these public routes.
• API-Version: 1 is optional on requests.
• Responses include API-Version: 1.0.3.
• Follow Next-Page-Cursor with the cursor query parameter.

Data assumptions

• Timezone-less timestamps are normalized by appending Z without port-timezone conversion.
• A missing source time is represented as T00:00:00Z.
• Cutoffs, terminal/facility codes, and universal service references are omitted when unavailable.
• isDummyVessel reflects IMO availability; unavailable vessel details are not invented.
• Port names and transport-call sequence numbers come from stored Atlas-derived fields.
• The source voyage string is duplicated into DCSA import/export voyage fields without claiming distinct semantics.
• DCSA service partners come from voyage carriers; stored schedule offering carriers stay separate in offeringServicePartners without invented voyage links.

Coverage limits

• Point-to-point routing is not implemented.
• inferredLegs only connect consecutive dated calls on the same vessel and voyage; they are not cargo-guaranteed routings.
• No 8–10 week schedule horizon is guaranteed.
• Only estimated arrival and departure timestamps are projected.

Vessel schedule example

curl -H 'API-Version: 1' \
'https://schedules.terminal49.com/vessel-schedules?carrierServiceCode=TPI'

Port schedule example

curl -H 'API-Version: 1' \
'https://schedules.terminal49.com/port-schedules?UNLocationCode=USNYC&date=2026-08-20'

Terminal49 catalogs

/services and /ports provide compact, searchable building blocks for discovery, LLM, and graph workflows. They are Terminal49 catalogs, not DCSA operations.