The API Report CardAPI Index
Rose Rocket

Rose Rocket API

roserocket.com

Rose Rocket runs a public REST API (v2) with OAuth 2.0 covering orders, quotes, invoices, manifests, and partner carriers through a unified object endpoint. Developer Portal access must be enabled on your account, and webhooks are thin: Order Status Change is the canonical event.

Last verified: August 2026Logistics & Supply ChainNO MCP
API GRADE
D
VERIFIED AUG 2026

SCORECARD

ExistenceGOODFirst class public REST API with a developer portal at roserocket.readme.io and a versioned v2 base URL.
AccessPOORDeveloper Portal access must be enabled on your account first; there is no self-serve sandbox.
CoverageGOODCustomers, orders, quotes, invoices, bills, manifests, assets, documents, and partner carriers are all documented objects.
AuthGOODOAuth 2.0: create an app in Account Settings, exchange client credentials for a standard Bearer token.
Docs & DXPOORTwo parallel doc sites plus legacy v1 pages blur the canonical reference; rate limits are not published.
StabilityMIXEDThe API is URL versioned at v2, but webhooks retry only 3 times at 30 second intervals, then drop; consumers reconcile by polling.
MCPNONENo official or community MCP server was found for Rose Rocket. The official MCP registry and GitHub show no servers targeting the platform. VERIFIED 2026-08
Supergood turns hard-to-integrate enterprise software into clean REST APIs and MCP tools: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Rose Rocket scores D on Supergood's API Report Card. Rose Rocket runs a public REST API (v2) with OAuth 2.0 covering orders, quotes, invoices, manifests, and partner carriers through a unified object endpoint. Developer Portal access must be enabled on your account, and webhooks are thin: Order Status Change is the canonical event.

Tried to integrate with Rose Rocket?
SOURCES
Webhook event catalog is narrow - Order Status Change is the canonical/default event; far fewer event types than Fleetio/Samsara roserocket.readme.io
No publicly documented rate-limit policy or quotas - integrators have to discover limits empirically platform.roserocket.com
Two parallel doc sites (platform.roserocket.com vs roserocket.readme.io, plus v1.0 legacy) create confusion about the canonical reference platform.roserocket.com
API access generally requires Developer Portal access enabled on the account - not a self-serve sandbox like Stripe/Plaid roserocket.readme.io
Webhook retries cap at 3 attempts with a 30-second delay - failed deliveries beyond that are dropped, requiring consumers to reconcile via polling platform.roserocket.com
Pre-built integration library (~20+ partners) trails larger TMS incumbents - users report some integrations are still being built out capterra.com
No GraphQL; everything goes through the unified `platformModel/objects` REST endpoint which can feel opaque vs resource-oriented REST roserocket.readme.io
Reporting filters are rigid - hard to build custom reports that fit the business g2.com
Invoicing workflow is repetitive - users re-enter similar details to create similar invoices g2.com
Integrations with third-party systems are 'slow progress' / still being developed capterra.com
Occasional minor bugs that have workarounds but persist between releases capterra.com
Transactional data sometimes updates with a delay across modules capterra.com
No public pricing - quoted per-seat/per-module after a sales call getapp.com
Best fit is mid-market carriers/brokers; smaller fleets cite it as feature-rich but pricey vs Tailwind / AscendTMS free tier truckpedia.io