Shipping Cohort Rate Engine

3PL providers integrate shipping engines with Slotted via API keys (inbound) and webhooks (outbound). This is not a ShipStation, EasyPost, or carrier plugin — you do not paste third-party carrier keys into Slotted.

At a glance

What it does

Connects your shipping rate engine to Slotted so that when a brand proposal needs transport rates, Slotted can ask your system for cohort-based rates and you can post results back.

Who it's for

3PL providers who already calculate shipping rates in their own systems and want those rates to flow into Slotted proposals. Operations leads can use this page to understand the loop; engineering implements the endpoints and webhooks.

How to use it

In Slotted, go to Profile → My Company → Transportation API and create sandbox keys. Configure your webhook URL.
Prove connectivity with a test webhook, then implement whoami, cohorts, ratings, and complete.
On a real proposal: receive a rating request → GET cohorts → POST ratings → POST complete. Use production keys only after sandbox works.

Contact

For access or questions, email admin@slotted.com.

Create and rotate keys in the Slotted app: Profile → My Company → Transportation API. Secrets are shown once.

Bidirectional model

Direction	What you configure	What happens
Slotted → you	Webhook URL (prod / sandbox)	`provider.integration.test` or `provider.rating.requested`
You → Slotted	`pk_…` / `sk_…` keys	`whoami`, GET cohorts, POST ratings

Authentication

Header	Required
`x-api-access-key`	Yes
`x-api-secret-key`	Yes
`x-slotted-environment`	Optional when prefix is ambiguous

Legacy x-api-key + referralCode is not the path for new integrations.

Core endpoints

GET /api/v1/three-pl/data-room/integration/whoami
GET /api/v1/three-pl/data-room/proposals/:proposalId/cohorts
POST /api/v1/three-pl/data-room/proposals/:proposalId/ratings
POST /api/v1/three-pl/data-room/proposals/:proposalId/ratings/complete

Shipping Cohort Rate Engine API reference →

Sandbox rules

Sandbox keys may call whoami and receive test webhooks
Sandbox keys must not read cohorts or submit rates for production proposals (403 SANDBOX_KEY_PRODUCTION_FORBIDDEN)

Outbound webhooks

Slotted POSTs to your webhook with the same API key headers. Verify both headers before processing. Events include provider.integration.test and provider.rating.requested. Typical loop: receive rating request → GET cohorts → POST ratings → POST complete.

Proving the full loop

Connectivity tests in the portal prove reachability and key validity — not a full carrier price. Prove end-to-end on a proposal: Transport → Send to engine → your system POSTs ratings.

Contact: Questions or need API access? Email admin@slotted.com.