Basic Concepts

Environments

Maven offers two environments for customers and third parties to use: staging and production.

The staging environment is intended to be used for integration development and testing. Most fleets start their integration projects on the staging environment and move to using production once final UAT / circle of service testing is performed and validated. Once your fleet is live on the production environment, the staging environment can continue to be used for further integration development or testing of new functionality before deploying to production.

The production environment is used for live operations of the Maven platform and is under the governance of Maven's production SLAs for uptime, performance, and monitoring.

While both environments are a duplicate of each other, there are a few differences to keep in mind:

• Maven utilizes a feature flagging and deployment system to allow customers to test new functionality that isn't fully rolled out to the general audience. Customers testing new or beta functionality may notice differences in API request and response schemas and feature behavior between staging and production.
• The two environments do not share data. This means any users, vehicles, company locations etc created in staging do not populate in production. This also applies for transactional data. Shipments, manifests, routes, etc.. created in staging do not populate in production.
• Maven provisions the environments with different levels of computing resurces. Performance numbers may vary between each environment.

Base URLs

For calling Maven's APIs, the following base URLs are used:

Production

https://integrations.mavenmachines.com/

Staging

https://integrations-staging.mavenmachines.com/

All API calls are performed by appending the API slug to the base URL. For example, to create a user in production, you would call

POST https://integrations.mavenmachines.com/users