Skip to main content
The sandbox environment allows you to test your integration with Obsidiam without affecting production data or incurring real transactions. It’s the perfect place to develop and validate your implementation before going live.

Why Use the Sandbox

Using our sandbox environment provides several benefits:
  • Risk-Free Testing: Test all API endpoints without affecting real data or triggering actual transactions
  • Development Flexibility: Experiment with different configurations and workflows
  • Debugging Support: Identify and fix issues in a controlled environment
  • Team Collaboration: Allow your development team to work simultaneously without conflicts
  • Isolated Data Sources: Sandbox uses fictive FX rates and does not connect to production data sources

Sandbox Base URL

All sandbox API requests should be directed to:
https://public-api.staging.obsidiam.com
Never use the sandbox URL or sandbox data for production workloads. The sandbox environment uses fictive FX rates and does not connect to our production data sources. Additionally, the environment may be reset periodically and does not guarantee data persistence.

Getting Access

1

Contact Our Team

To gain access to the sandbox environment, please contact our team. We’ll provide you with the necessary credentials and guide you through the setup process.
2

Receive Sandbox Credentials

Once approved, you’ll receive sandbox-specific credentials including an API key and access to create test applications.
3

Configure Your Application

Set up your application to use the sandbox base URL and credentials. Ensure your development environment is properly configured before making requests.

Sandbox vs Production

FeatureSandboxProduction
Base URLpublic-api.staging.obsidiam.compublic-api.obsidiam.com
Real TransactionsNoYes
Data PersistenceLimitedGuaranteed
Rate LimitsRelaxedStandard

Best Practices

  • Separate Credentials: Use different API keys for sandbox and production environments
  • Environment Variables: Store your base URL in environment variables to easily switch between environments
  • Thorough Testing: Test all edge cases and error scenarios before moving to production
  • Monitor Responses: Pay attention to API responses and error messages during development

Next Steps