Skip to main content

Environments

Debitura provides separate environments for development and production.

Sandbox Environment

Use the sandbox environment for development and testing.

Base URL: https://api.sandbox.debitura.com

Characteristics:

  • Isolated test environment
  • No real money or legal actions
  • Test data only
  • Full API feature parity with production
  • Faster processing times for testing

Use cases:

  • Initial integration development
  • Testing edge cases and error handling
  • Validating webhook implementations
  • Training and demos
tip

Request sandbox API credentials through your account manager or the Support Center.


Production Environment

Use the production environment for live cases with real legal and financial consequences.

Base URL: https://api.debitura.com

Characteristics:

  • Live environment with real cases
  • Actual debt collection activities
  • Real money transfers
  • Legal compliance required
  • Standard processing times

Use cases:

  • Live customer cases
  • Production integrations
  • Real invoicing and payments
warning

Production API access requires completed onboarding, compliance verification, and signed agreements.


Environment Differences

FeatureSandboxProduction
API Base URLapi.sandbox.debitura.comapi.debitura.com
AuthenticationSandbox API keysProduction API keys
DataTest data onlyReal customer data
Legal actionsSimulatedReal legal processes
PaymentsSimulatedReal money transfers
Processing timeAcceleratedStandard
WebhooksSupportedSupported

Best Practices

During Development

  1. Always start development in sandbox
  2. Test all error scenarios
  3. Validate webhook handling
  4. Test idempotency and retries
  5. Verify data mappings

Before Production

  1. Complete integration testing in sandbox
  2. Perform security audit
  3. Review compliance requirements
  4. Obtain production credentials
  5. Configure production webhooks
  6. Plan cutover strategy

In Production

  1. Monitor API usage and errors
  2. Set up alerting for failures
  3. Keep sandbox in sync for testing
  4. Test new features in sandbox first
  5. Maintain error logging