Environments
The Adapt2Move Mobility API provides two separate environments — Test and Production — so you can build and verify your integration before going live. Both environments are accessed through the same base URL (https://adapt2move.de/mobility-api/v2/), and the environment is determined entirely by the API key you use. Secret test keys are prefixed with a2m_test_ and production keys with a2m_live_. Publishable keys follow the same convention: a2m_pk_test_ for test and a2m_pk_live_ for production. There is no separate hostname or URL path to remember; swapping the key is all it takes to switch environments.
Test Environment
The test environment is designed for development and integration work. When you search for vehicles using a test key, the API connects to provider sandbox systems where available, so the search results you receive reflect real offers from test systems with realistic data structures. However, bookings made in test mode are not forwarded to the actual providers. Instead, they are simulated and confirmed immediately, which means you can exercise the full booking workflow — from search through prebook to final booking — without incurring any costs or creating real reservations. This makes the test environment ideal for automated testing, CI pipelines, and iterative development.
Bookings created with a test API key are simulated. They do not result in real reservations with providers and will never incur charges.
Production Environment
The production environment connects to live provider systems. Every booking you create with a production key is real and binding. Standard policies, fees, and cancellation terms apply to all production bookings, so make sure your integration has been thoroughly tested before switching to production keys. You should treat production bookings with the same care as any real commercial transaction.
Developing with Environments
The recommended workflow is to develop and test your integration entirely against the test environment first. Once you are confident that your implementation handles searches, prebookings, bookings, and error cases correctly, switch to production by replacing your test API key with your production key. Because both environments share the same base URL and API contract, no other code changes are required.
To go from test to production, replace your a2m_test_ key with your a2m_live_ key (or a2m_pk_test_ with a2m_pk_live_ for publishable keys). The base URL, endpoints, request formats, and response structures remain identical regardless of key type.
Rate Limits
Rate limits may differ between environments. The test environment is generally more lenient to accommodate rapid iteration during development, while the production environment enforces stricter limits appropriate for live traffic. If you encounter rate limit errors during testing, they are unlikely to carry over to production at the same thresholds, but you should still design your integration to handle 429 Too Many Requests responses gracefully in both environments.
Data Isolation
Test and production data are completely isolated from each other. A booking created with a test key cannot be retrieved, modified, or cancelled using a production key, and vice versa. This separation extends to all resources — offers, bookings, and any associated references exist only within the environment where they were created. If you need to verify a booking in a specific environment, make sure you are using the corresponding API key.
There is no way to access test data from production or production data from test. Always ensure you are using the correct API key for the environment you intend to work with.