Environments

View as Markdown

Rendr provides two fully isolated API environments. Use UAT for development and testing, and Production for live traffic.


Base URLs

UAT
https://uat.api.rendr.delivery
Production
https://api.rendr.delivery

All API paths are identical across environments. Only the base URL changes.


Environment Isolation

Environments are completely separated — nothing is shared between them.

UATProduction
API keysUAT-specificProduction-specific
DeliveriesIsolatedIsolated
WebhooksConfigured independentlyConfigured independently
Carrier integrationsSandbox / controlled test modeLive
Financial settlementNot appliedMay apply

Data created in UAT does not exist in Production.


UAT (User Acceptance Testing)

UAT is intended for integration development and pre-production validation.

Use UAT for:

Integration Development

Build and iterate against a safe, non-live environment.

End-to-End Testing

Validate full delivery flows without real-world impact.

Status Lifecycle Testing

Walk through status transitions in a controlled environment.

Store Configuration

Set up and test store rules before going live.

Characteristics:

  • Safe for repeated testing
  • Test deliveries do not trigger real financial settlement
  • Carrier integrations operate in sandbox or controlled test mode
  • Rate limits may differ from Production

Always validate your integration in UAT before promoting changes to Production.


Production

Production processes live deliveries with real carriers and real customers.

Characteristics:

  • Real carrier bookings
  • Real dispatch and tracking
  • Financial settlement may apply
  • Operational monitoring enabled

Only Production API keys can access the Production environment.