Forto
Forto is a digital freight forwarder and supply chain platform that combines technology with logistics expertise to provide sea, air, and rail freight services across 100+ countries. The platform offers a public REST API for booking management, shipment tracking, transport plans, document handling, and webhook subscriptions, enabling shippers, enterprises, and partners to integrate Forto freight operations directly into their ERP, TMS, and supply chain systems via standard HTTPS APIs, EDI, or fully customized integrations.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Forto the way a machine reads it — 31 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Forto scores 44.7/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Forto
Each block below is one kind of artifact we hold for Forto. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Forto Public API
The Forto Public API provides programmatic access to Forto's digital freight forwarding platform. It exposes booking management (create, update, finalize, discard, list), shipme...
Forto Bookings API
The Bookings API from Forto — 4 operation(s) for bookings.
Forto Documents API
The Documents API from Forto — 2 operation(s) for documents.
Forto Shipments API
The Shipments API from Forto — 2 operation(s) for shipments.
Forto Subscriptions API
The Subscriptions API from Forto — 3 operation(s) for subscriptions.
Forto Tokens API
The Tokens API from Forto — 2 operation(s) for tokens.
Forto TransportPlans API
The TransportPlans API from Forto — 4 operation(s) for transportplans.
Scroll within the panel for all 7 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Forto Public API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Forto Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Forto Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Forto Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
REST API
Public HTTPS REST API exposing booking, shipment, transport plan, document, and subscription endpoints
EDI Integrations
Predefined EDI-based integrations for core data exchange with shipper systems
Webhook Subscriptions
Create, list, and delete subscriptions to receive notifications on shipment and booking changes
Transport Plan Tracking
Multi-version transport plan API with 30+ milestone events at shipment and container level
Document Management
Upload and download shipment documents, invoices, and reports via API
Token-based Authentication
Create, list, and delete API tokens for authenticating requests
FortoLabs Agentic AI
AI solutions for the logistics industry providing agentic AI capabilities for logistics operations
Scroll within the panel for all 7 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
ERP / TMS Integration
Connect Forto shipments and bookings directly into SAP, Oracle, Infor Nexus, and other enterprise systems
Real-Time Shipment Visibility
Surface live transport milestones into supply chain dashboards and control towers
Booking Automation
Programmatically create, update, and finalize freight booking requests across sea, air, and rail
Event-Driven Workflows
Subscribe to webhooks to trigger downstream workflows when shipment status changes
Sustainability Reporting
Pull emissions and Climate Visibility data into ESG and sustainability reporting
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
SAP
Integrate Forto shipment data into SAP ERP and supply chain modules
Oracle
Connect Forto bookings and tracking events into Oracle ERP and SCM applications
Infor Nexus
Exchange shipment and booking data with the Infor Nexus supply chain network
EDI
Predefined EDI integrations for standardized B2B freight data exchange
Resources
Every other property we hold for Forto — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/forto · machine-readable index on apis.io