Entitlements and Paid Features

Understand which Terminal49 API, map, widget, vessel, rail, and MCP features require additional account enablement and what non-entitled callers receive.

Some Terminal49 features require account enablement beyond standard API access.

Entitlement overview

Surface	Entitlement	How to request access	Non-entitled behavior
Container Map GeoJSON API (GET /v2/containers/{id}/map_geojson)	Routing Data	Contact [e-mail]	403 Forbidden with Routing data feature is not enabled for this account
Vessel position and future-position endpoints	Routing Data / vessel positions	Contact [e-mail]	403 Forbidden with Routing data feature is not enabled for this account
MCP get_container_route tool	Routing Data	Contact [e-mail]	The tool returns a feature-not-enabled response; use get_container_transport_events for historical milestones
Terminal49 Map Embed	Publishable map API key	Contact [e-mail]	The browser embed cannot authenticate without a valid publishable key
Tracking Widget Embed	Publishable widget API key	Contact [e-mail]	The browser widget cannot authenticate without a valid publishable key
Rail LFD data (import_deadlines.pickup_lfd_rail and the container.pickup_lfd_rail.changed webhook event)	Rail Plan	Contact [e-mail]	container.pickup_lfd_rail.changed notifications are not delivered, and rail-carrier LFD updates are not surfaced on the container

Pricing

See Pricing for current public pricing pointers. If a page says to contact sales or support, treat that feature as account-gated until the entitlement appears on your account.

Related pages

• Vessel and Container Route Data
• Terminal49 Map Embed Guide
• Tracking Widget Embed Guide
• Rail Integration Guide
• MCP Server