Sandbox Environment

The Gett sandbox environment allows you to test all order flows without creating real bookings or incurring charges. The sandbox fully replicates production behavior, letting you validate your integration before going live.

πŸ“˜

Safe Testing Environment

Test all API functionality without real orders, drivers, or charges. The sandbox behaves identically to production.

Getting Started

Sandbox Endpoint

https://api.sandbox.gett.com

Replace the production base URL with the sandbox URL in your integration. All endpoints remain the same.

Credentials

Contact Gett to receive separate sandbox credentials:

  • Sandbox Client ID
  • Sandbox Client Secret
  • Sandbox Partner ID

❗️

Keep Credentials Separate

Always use sandbox credentials for testing and production credentials for live operations. Never mix them.

What You Can Test

The sandbox supports testing all functional flows:

Authentication Flow

  • Obtain access tokens using your sandbox credentials
  • Test token expiration and renewal
  • Validate error handling for invalid credentials

Pricing & Availability Flow

  • Request pricing estimates for different routes
  • Test multi-stop journeys
  • Check service availability in different areas
  • Verify pricing for immediate vs scheduled bookings
  • Test both supported locales (English and Hebrew)

Order Lifecycle Flow

  • Create orders - Test immediate and scheduled bookings
  • Track orders - Monitor order status changes from creation to completion
  • Get order details - Retrieve real-time information including driver details and ETA
  • Cancel orders - Test cancellation at different order stages

Order Status Progression

Test how orders move through different states:

  • Pending β†’ Order created
  • Reserved β†’ Scheduled for future (not yet dispatched)
  • Unreserved β†’ Future order released from schedule
  • Routing β†’ Finding a driver
  • Confirmed β†’ Driver assigned and en route
  • Waiting β†’ Driver at pickup location
  • Driving β†’ Journey in progress
  • Completed / Cancelled / Rejected β†’ Terminal states
  • CareReq β†’ Manual support intervention

Error Handling Flow

  • Invalid coordinates or addresses
  • Missing required parameters
  • Invalid phone number formats
  • Malformed requests
  • Rate limiting scenarios

Edge Cases

  • Long-distance routes
  • Multi-stop complex journeys
  • Special characters in names and addresses
  • Maximum passenger and luggage limits

Testing Checklist

Before going to production, test these essential flows:

βœ… Core Flows

  • Authenticate and obtain access token
  • Get pricing estimates for various routes
  • Create immediate booking
  • Create scheduled booking (future pickup)
  • Create multi-stop journey
  • Retrieve order details
  • Track order status changes
  • Cancel an order

βœ… Localization

  • Test with English locale (en)
  • Test with Hebrew locale (he)

βœ… Error Scenarios

  • Handle invalid authentication
  • Handle invalid coordinates
  • Handle missing required fields
  • Handle network timeouts
  • Handle order not found errors

βœ… Real-World Scenarios

  • Rush hour pricing (surge scenarios)
  • Early morning scheduled rides
  • Airport pickups with flight tracking
  • Business district to residential area routes

Best Practices

Configure Environment Switching

Set up your application to easily switch between sandbox and production:

const config = {
  sandbox: {
    baseURL: 'https://api.sandbox.gett.com',
    clientId: 'your_sandbox_client_id',
    clientSecret: 'your_sandbox_client_secret',
    partnerId: 'your_sandbox_partner_id'
  },
  production: {
    baseURL: 'https://api.gett.com',
    clientId: 'your_production_client_id',
    clientSecret: 'your_production_client_secret',
    partnerId: 'your_production_partner_id'
  }
};

const env = process.env.NODE_ENV === 'production' ? 'production' : 'sandbox';
const apiConfig = config[env];

Test Regularly

  • Run sandbox tests before each deployment
  • Include sandbox tests in your CI/CD pipeline
  • Verify all flows after API updates or changes

Monitor Behavior

  • Compare sandbox responses with production behavior
  • Document any differences you observe
  • Report discrepancies to Gett support

Moving to Production

Once you've successfully tested all flows in sandbox:

  1. Verify all checklist items are complete
  2. Update your configuration to use production credentials
  3. Change the base URL from https://api.sandbox.gett.com to https://api.gett.com
  4. Start with small volume and gradually increase
  5. Monitor production orders closely during initial rollout

βœ…

Ready to Go Live

After comprehensive sandbox testing, you're ready to switch to production and start accepting real orders!