Going Live on Production
Move your integration from the sandbox to the production environment.
Once you've built and tested against the sandbox, going live is a matter of production access, production credentials, an activated subscription, and pointing your integration at the production host. The request/response shapes and your integration code do not change.
Before you start
Complete your integration in the sandbox first, see Quick Start Setup and Sandbox Testing. This page only covers what's different in production.
1. Get production access
Register your organisation on the production dashboard with your business details and select your market as the tenant.
2. Onboard your team
Submit your team members for whitelisting. Once Spare confirms, invite them from the dashboard; they accept to gain access.
3. Generate production credentials
Under Settings → Developer Tools, create your production API Key and App ID. Production and sandbox credentials are separate, the sandbox pair does not work against production.
Server-side only
Store your API Key and App ID server-side. Keep them out of any mobile app, browser, or client-facing code.
4. Subscription activation
Your Spare account manager activates your production subscription once steps 1–3 are complete. You receive written confirmation that production is live for your account, your API calls will not succeed against production until this is done.
5. Switch the base URL
Point every request at the production host. Nothing else about the request changes.
Keep the x-tenant: UAE header and authenticate with Authorization: Bearer <access-token>.
| Environment | Base URL |
|---|---|
| Sandbox | https://api.sandbox.tryspare.ae |
| Production | https://api.tryspare.ae |
See Sandbox Testing → Switching environments for how the environment and credential pair line up.
Pre-launch checklist
- Team members accepted their dashboard invitations
- Production API Key + App ID generated and stored server-side
- Production subscription confirmed active by your account manager
- Base URL switched to your production host with the correct auth headers
- Webhook / callback endpoints point at your production URLs (HTTPS)
- Redirect URLs are HTTPS and registered with Spare
- Ran your integration end-to-end and exercised failure paths
Key takeaways
- Production uses separate credentials and its own host, the API contract is identical to sandbox.
- Your account manager activates the production subscription; calls fail against production until it's confirmed.
- Keep credentials server-side; verify webhooks and redirect URLs are production HTTPS before launch.