Entitlements and Paid Features

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 sales@terminal49.com	`403 Forbidden` with `Routing data feature is not enabled for this account`
Vessel position and future-position endpoints	Routing Data / vessel positions	Contact sales@terminal49.com	`403 Forbidden` with `Routing data feature is not enabled for this account`
MCP `get_container_route` tool	Routing Data	Contact sales@terminal49.com	The tool returns a feature-not-enabled response; use `get_container_transport_events` for historical milestones
Terminal49 Map Embed	Publishable map API key	Contact support@terminal49.com	The browser embed cannot authenticate without a valid publishable key
Tracking Widget Embed	Publishable widget API key	Contact support@terminal49.com	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 sales@terminal49.com	`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.

Terminal49 API Pricing

Terminal49 Test Tracking Numbers

⌘I

Getting Started

Tracking Fundamentals

Webhooks & Events

Integrations & Embeds

Platform & Reference

Entitlements and Paid Features

Entitlement overview

Pricing

​Entitlement overview

​Pricing

​Related pages

Entitlement overview

Pricing

Related pages