Learn about the Sandbox environment, its features, limitations, and how to use it for API testing.
The Sandbox is a dedicated testing environment that allows clients to integrate and interact with our APIs in a safe and controlled manner. It is designed to mirror the Production environment as closely as possible, providing a realistic experience without real-world consequences.
This environment enables developers and testers to explore our platform, validate their integrations, and troubleshoot issues without relying on live third-party services. Instead, the Sandbox uses mocked data to simulate real-world responses.
https://sandbox-integration-api.meshconnect.com
β
Developers & Engineers β Validating API integrations and troubleshooting issues.
β
Quality Assurance Teams β Testing workflows before Production deployment.
β
Product Teams β Understanding platform behavior and testing use cases.
The easiest and quickest way to get started is through our Interactive Demos. Try various Mesh products without any set up or touching βrealβ assets as shown below,
Alternatively, you can start interacting with various Sandbox endpoints following the API reference
Create Sandbox API keys:
Use the Dedicated API Endpoint:
https://sandbox-integration-api.meshconnect.com
Authenticate Using API Credentials:
Test Your Integration:
Move to Production:
πΉ Can I perform real transactions in the Sandbox?
No, the Sandbox does not process real transactions. All payments, asset movements, and third-party API calls return mocked responses for testing purposes.
πΉ Does the Sandbox have the same API as Production?
Yes, the Sandbox API follows the same structure and endpoints as the Production API, but the responses are simulated.
πΉ Are Testnets supported?
Currently, Sepolia network is supported for Metamask and Rainbow. Please read more about how to set them up in your sandbox in this Guide.
πΉ Are all exchange integrations supported in the Sandbox the same as in Production?
No, the Sandbox API supports the following exchange integrations:
Exchanges |
---|
Binance |
Binance API |
Coinbase |
Bybit |
OKX API |
Gemini |
KuCoin API |
Kraken API |
πΉ How can I allow users to bypass authentication when they return to use Mesh again?
To enable a seamless return experience without prompting users to authenticate again, you can pass a valid accessToken
into the createLink()
function when connecting an account via the Mesh Web SDK.
If you provide a valid accessToken
, users will not need to reauthenticate.
If you pass no integrationId
and no accessToken
, the catalog will open, but users will be required to authenticate again when selecting an already linked integration.
Important: You must securely store and manage the accessToken
on your side. For best practices on handling authentication tokens, refer to our guide: Handling Auth Tokens.
Learn about the Sandbox environment, its features, limitations, and how to use it for API testing.
The Sandbox is a dedicated testing environment that allows clients to integrate and interact with our APIs in a safe and controlled manner. It is designed to mirror the Production environment as closely as possible, providing a realistic experience without real-world consequences.
This environment enables developers and testers to explore our platform, validate their integrations, and troubleshoot issues without relying on live third-party services. Instead, the Sandbox uses mocked data to simulate real-world responses.
https://sandbox-integration-api.meshconnect.com
β
Developers & Engineers β Validating API integrations and troubleshooting issues.
β
Quality Assurance Teams β Testing workflows before Production deployment.
β
Product Teams β Understanding platform behavior and testing use cases.
The easiest and quickest way to get started is through our Interactive Demos. Try various Mesh products without any set up or touching βrealβ assets as shown below,
Alternatively, you can start interacting with various Sandbox endpoints following the API reference
Create Sandbox API keys:
Use the Dedicated API Endpoint:
https://sandbox-integration-api.meshconnect.com
Authenticate Using API Credentials:
Test Your Integration:
Move to Production:
πΉ Can I perform real transactions in the Sandbox?
No, the Sandbox does not process real transactions. All payments, asset movements, and third-party API calls return mocked responses for testing purposes.
πΉ Does the Sandbox have the same API as Production?
Yes, the Sandbox API follows the same structure and endpoints as the Production API, but the responses are simulated.
πΉ Are Testnets supported?
Currently, Sepolia network is supported for Metamask and Rainbow. Please read more about how to set them up in your sandbox in this Guide.
πΉ Are all exchange integrations supported in the Sandbox the same as in Production?
No, the Sandbox API supports the following exchange integrations:
Exchanges |
---|
Binance |
Binance API |
Coinbase |
Bybit |
OKX API |
Gemini |
KuCoin API |
Kraken API |
πΉ How can I allow users to bypass authentication when they return to use Mesh again?
To enable a seamless return experience without prompting users to authenticate again, you can pass a valid accessToken
into the createLink()
function when connecting an account via the Mesh Web SDK.
If you provide a valid accessToken
, users will not need to reauthenticate.
If you pass no integrationId
and no accessToken
, the catalog will open, but users will be required to authenticate again when selecting an already linked integration.
Important: You must securely store and manage the accessToken
on your side. For best practices on handling authentication tokens, refer to our guide: Handling Auth Tokens.