Technical Onboarding to Sandbox
Provide your company details, receive your Sandbox client_id and client_secret, and connect to the Movmint Sandbox environment.
Overview
After your organization is approved in Business Onboarding, you move on to Technical Onboarding. At this stage Movmint issues your API credentials for the Sandbox environment so you can begin integrating against test networks.
What Movmint needs from you
To issue your Sandbox credentials, Movmint requires the following details for your organization:
| Field | Description |
|---|---|
| Company name | Your legal company name, matching what was approved during Business Onboarding. |
| Address | Your registered business address. |
| Phone number | A primary business contact phone number. |
| Tax ID | Your company tax identifier (e.g., EIN/TIN), used for compliance and reporting. |
What Movmint issues to you
Once your details are verified, Movmint provisions an OAuth 2.0 client and issues:
| Credential | Description |
|---|---|
client_id | A public identifier for your application. |
client_secret | A confidential secret used to authenticate. Treat this like a password. |
These credentials are scoped to the Sandbox environment and to the Products configured for your organization.
Keep your client secret confidentialNever commit your
client_secretto version control, embed it in client-side or mobile code, or share it over insecure channels. Store it in a secrets manager or environment variable. If you believe a secret has been exposed, contact Movmint immediately to have it rotated.
The Sandbox environment
Sandbox is a near-exact copy of Production, kept in lockstep with Production releases. The only differences are that Sandbox operates against test networks and test payment providers, so no real funds move.
| Configuration | Production | Sandbox |
|---|---|---|
| Base URL | https://api.movmint.io | https://api.sandbox.movmint.io |
| Ethereum network | mainnet | testnet (Sepolia) |
| Base network | mainnet | testnet (Sepolia) |
| Bitcoin network | mainnet | testnet3 |
| Wallet address generation | Production | Testnet |
All endpoints, request formats, status codes, and error semantics are identical across Sandbox and Production. Code you write against Sandbox will work unchanged in Production once you swap the base URL and credentials.
Verify your credentials
The fastest way to confirm your credentials work is to request an access token. Exchange your client_id and client_secret for a bearer token against the Sandbox token endpoint:
curl -X POST https://api.sandbox.movmint.io/oauth2/token \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=client_credentials" \
-d "client_id=YOUR_CLIENT_ID" \
-d "client_secret=YOUR_CLIENT_SECRET" \
-d "scope=openid"A 200 response containing an access_token confirms your credentials are valid. See Authentication & Authorization for the full flow and code examples in Go, TypeScript, Java, Rust, and Python.
Next steps
With working Sandbox credentials, build out your integration and then schedule your Sandbox Test with Movmint to verify your integration pattern.
Updated 2 months ago
