{
  "object": "doc",
  "title": "How do I get help with the Cartroute API?",
  "description": "Support channels, status page, changelog and versioning policy.",
  "section": "Resources",
  "url": "https://cart-route.com/docs/support",
  "updated": "2026-09-23",
  "prev": "https://cart-route.com/docs/machine-readable",
  "next": null,
  "text": "Email [support@cart-route.com](mailto:support@cart-route.com) with the `request_id` from the response you are asking about. Live system status is at [/status](https://cart-route.com/status), API changes are in the [changelog](https://cart-route.com/changelog), and breaking changes only ship under a new dated API version.\n\n## What should I include in a support request?\n\n- The `request_id` (in every response body and in the `X-Request-Id` header).\n\n- The endpoint, the parameters and the time in UTC.\n\n- The error `code` if there was one. Never send your API key.\n\n## How is the API versioned?\n\nThe current version is `2026-09-01`, reported as `api_version` in every metered response. Adding fields, endpoints, error codes or enum values is not a breaking change, so clients should ignore unknown fields. Removing or renaming a field, or changing its meaning, ships under a new dated version announced at least 90 days ahead.\n\n## Where do I check whether something is down?\n\n[/status](https://cart-route.com/status) shows the API, MCP server, website and price pipeline, with last-hour request counts, latency and server errors. [`/status?format=json`](https://cart-route.com/status?format=json) is suitable for monitoring.\n\n## How do I report a security issue?\n\nEmail [security@cart-route.com](mailto:security@cart-route.com); see [security.txt](https://cart-route.com/.well-known/security.txt). Good-faith research that respects user privacy and service availability is welcome.\n\n## Who do I talk to about volume pricing?\n\n[sales@cart-route.com](mailto:sales@cart-route.com)."
}