← Back to all docs

Rose Rocket API

Rose Rocket is an AI-native transportation management platform (TMS) and supply chain ERP for freight brokerages, trucking carriers, and 3PLs, managing orders, manifests, carriers, customers, and billing. Its API lets you programmatically pull orders, shipments, manifests, partner carriers, quotes, invoices, and documents—and push updates like new orders, dispatch assignments, financial line items, and status changes back into Rose Rocket.

By Alex KlarfeldMay 30, 2026
Rose Rocket API

What is Rose Rocket?

Rose Rocket is an AI-native transportation management platform (TMS) and supply chain ERP built for freight brokerages, trucking carriers, and supply chain operations. Customers use Rose Rocket to manage orders and quotes, dispatch and manifest shipments, onboard and assign partner carriers, run customer and carrier portals, track loads, and handle billing, invoicing, and settlements—processing billions of dollars in freight across more than 100,000 users.

Core product areas include:

  • TMS.ai (order management, dispatch, manifesting, and shipment tracking)
  • Supply Chain ERP platform (infrastructure, business logic, and customization layers)
  • Customer and carrier portals for self-service quoting, booking, and tracking
  • Billing, invoicing, financial line items, and settlements
  • AI assistants—TED (email-to-order), Rosie (order insights), and Rocky (onboarding/optimization)

Common data entities:

  • Customers, Contacts, Addresses, Tags
  • Orders, Quotes, Commodities, Tasks
  • Manifests, Partner Carriers, Assets
  • Invoices, Bills, Financial Line Items, Tax Rates
  • Documents and webhook Events

The Rose Rocket Integration Challenge

Brokerages and carriers run daily operations on Rose Rocket, but turning its portal and API surfaces into reliable, production-grade automation involves real friction:

  • OAuth 2.0 setup: API access requires creating an OAuth application, managing client ID/secret, and handling the authorize/token flow with the correct audience parameter
  • Versioned, split base URLs: Endpoints span v1 (platform.roserocket.com/api/v1) and v2 (network.roserocket.com/api/v2), so integrations must reconcile object models across versions
  • Nested object relationships: Orders, manifests, legs, commodities, and financial line items are deeply linked—pulling complete records requires the right paths query parameters
  • Tenant-specific configuration: Custom tags, financial line items, and tax rate components vary per account, breaking generic integrations
  • Webhook reliability: Event delivery for order and status changes must be captured, retried, and reconciled against API state
  • Document workflows: BOLs, PODs, and rate confirmations need careful upload/download handling alongside structured order data

How Supergood Creates Rose Rocket APIs

Supergood wraps Rose Rocket's OAuth flow, REST API, and authenticated portal surfaces into a single resilient API layer for your account—normalizing orders, manifests, carriers, and billing into consistent objects so you integrate once.

  • Manages OAuth 2.0 client credentials, token exchange, and audience handling securely
  • Maintains session continuity with automated token refresh and change detection
  • Reconciles v1 and v2 endpoints and resolves nested objects via paths so you get complete records
  • Captures webhook events for orders and status changes with retry and replay handling

Use Rose Rocket with AI agents: Rose Rocket MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your modules, object scope, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready Rose Rocket adapter tailored to your account configuration and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Rose Rocket evolves.

rose rocket

API Endpoints

Authentication

POST/authenticate

Authenticate via OAuth 2.0 client credentials and obtain a bearer access token for downstream Rose Rocket API calls.

Orders

GET/orders

List orders with filters for customer, status, pickup/delivery date, and tags across the account.

Orders

POST/create_order

Create a new order with customer, commodities, addresses, and financial line items in a single request.

Manifests

GET/manifests

Retrieve manifests and their assigned partner carriers, legs, and dispatch status.

Carriers

GET/partner_carriers

List partner carriers, their contacts, assets, and onboarding/compliance status.

Billing

GET/invoices

Pull invoices, bills, and financial line items with customer, status, and date filters.

Use Cases

Sync orders and shipments into your data warehouse

- Pull orders, quotes, and commodities into a central warehouse for reporting - Stream manifest and status-change events to downstream BI and tracking tools - Reconcile customer and address records across systems for a unified view

Automate dispatch and partner carrier assignment

- Create manifests and assign partner carriers programmatically - Push dispatch updates and tracking status back to customers without portal clicks - Trigger carrier onboarding and compliance checks from your own systems

Reconcile billing and settlements

- Sync invoices, bills, and financial line items into accounting and AR systems - Match carrier settlements and chargebacks against orders and manifests - Surface unbilled or overdue orders to finance workflows

Power AI agents and automated order intake

- Convert inbound emails and EDI into structured orders via the API - Feed normalized order and tracking data to AI agents and MCP servers - Attach BOLs, PODs, and rate confirmations to the correct order records

Technical Specifications

Authentication

OAuth 2.0 client ID/secret with bearer access tokens, handled in a managed session

Connectivity

Rose Rocket REST API (v1 platform and v2 network base URLs) plus authenticated portal surfaces

Response format

Normalized JSON across Orders, Manifests, Carriers, and Billing objects

Rate limits

Adaptive throttling tuned to your account to stay within Rose Rocket API limits

Session management

Automatic OAuth token refresh, audience handling, and credential rotation

Data freshness

Near real-time pulls for orders, manifests, and invoices with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for order creation, status changes, and manifest updates

Latency

Sub-second reads on cached entities; multi-second writes when posting orders and financial line items

Throughput

Horizontally scaled workers sized to high-volume brokerage and carrier order flow

Reliability

Retry, backoff, and idempotency keys for order creation and billing transactions

Adaptation

Continuous monitoring of Rose Rocket API releases and account-specific configuration drift

Frequently asked questions

Yes. Rose Rocket offers a public OAuth 2.0 REST API with CRUD operations across orders, manifests, customers, partner carriers, invoices, and more. Supergood wraps it into a normalized, resilient layer and adds session management, webhook handling, and adaptation as the platform evolves.

Rose Rocket uses OAuth 2.0. You create an OAuth application to get a client ID and secret, then exchange them for a bearer access token. Supergood manages the full authorize/token flow, audience parameters, and automatic token refresh for you.

Yes. Endpoints span the v1 platform and v2 network base URLs with different object models. Supergood reconciles both versions and resolves nested objects so you receive complete, consistent records regardless of which version exposes them.

Yes. Rose Rocket sends webhook Events—such as when an order is created—to URLs registered in your account. Supergood captures these events with retry and replay handling and reconciles them against API state.

Each account is profiled against its configured tags, financial line items, and tax rate components. Supergood preserves these account-specific fields rather than forcing a generic schema.

Ready to get a real API?