FORYN OCEAN / DEVELOPERS

Connect your forwarding systems to Foryn.

Submit carrier-confirmed bookings. Receive structured commercial assessments and consequential exceptions. Keep your existing TMS and booking workflow.

Start integrating →Browse API reference

Documented implementation. Production access is coordinated directly; no public sandbox or credentials.

Three endpoints. One booking contract.

The public reference describes the implemented Ocean API, not planned administrative capabilities.

POST/api/ocean/v1/bookingsOne confirmed booking, amendment or cancellation POST/api/ocean/v1/messagesSupported EDI profiles and partial event extracts POST/api/ocean/v1/exceptions/{exceptionId}/resolutionsOptional source-attributed resolution

Build with a specification, not assumptions.

01 / SPECIFICATIONOpenAPI 3.1 JSON ↗

Directly fetchable machine-readable request and response contracts.

02 / AUTOMATIONAI coding-agent playbook →

A source-to-Foryn mapping procedure with explicit missing-data rules.

03 / TEST DATASynthetic booking example ↗

Valid JSON ready for local contract tests. No customer data.

04 / GUIDANCEAgent instructions ↗

Portable integration instructions for your own repository.

Documentation

Integrate

Booking Integration ↗Commercial Exceptions ↗Exception Resolution ↗Batch Integration ↗EDI and Standards ↗Reference Data ↗

Build and verify

Integration Testing ↗AI Coding Agents ↗Versions and Changelog ↗

Foryn is responsible for commercial evaluation. Your integration is responsible for source authenticity, stable booking IDs and correct revision order.