API Environments

AgentSync provides multiple environments for different stages of development and testing. This guide covers environment configuration and best practices.

Available Environments

Development

Purpose: Feature development and early testing

ServiceURL
API Basehttps://api.dev.agentsync.io
Authhttps://auth.dev.agentsync.io
Internalhttps://api-internal.dev.agentsync.io

Characteristics:

  • Most frequent deployments
  • May have experimental features
  • Data is regularly refreshed
  • Lower performance guarantees

Test

Purpose: Integration and regression testing

ServiceURL
API Basehttps://api.test.agentsync.io
Authhttps://auth.test.agentsync.io
Internalhttps://api-internal.test.agentsync.io

Characteristics:

  • Stable feature set
  • Used for CI/CD integration tests
  • Data is periodically refreshed
  • Mirrors production configuration

Sandbox

Purpose: User Acceptance Testing (UAT)

ServiceURL
API Basehttps://api.sandbox.agentsync.io
Authhttps://auth.sandbox.agentsync.io
Internalhttps://api-internal.sandbox.agentsync.io

Characteristics:

  • Production-like environment
  • Used for customer demos
  • More stable than Test
  • Data changes require approval

Production

Purpose: Live production services

ServiceURL
API Basehttps://api.agentsync.io
Authhttps://auth.agentsync.io
Internalhttps://api-internal.agentsync.io

Characteristics:

  • Highest availability guarantees
  • Strict change management
  • Real customer data
  • Full monitoring and alerting

Environment Selection Guide

Use CaseRecommended Environment
Building new featuresDevelopment
Running automated testsTest
Customer demosSandbox
Production integrationsProduction
Load testingTest (coordinate with DevOps)
Security testingDevelopment

Configuration Example

Environment Variables

# Development
export API_BASE_URL=https://api.dev.agentsync.io
export AUTH_URL=https://auth.dev.agentsync.io/oauth/token

# Test
export API_BASE_URL=https://api.test.agentsync.io
export AUTH_URL=https://auth.test.agentsync.io/oauth/token

# Sandbox
export API_BASE_URL=https://api.sandbox.agentsync.io
export AUTH_URL=https://auth.sandbox.agentsync.io/oauth/token

# Production
export API_BASE_URL=https://api.agentsync.io
export AUTH_URL=https://auth.agentsync.io/oauth/token

Python Configuration

import os

ENVIRONMENTS = {
    "development": {
        "api_base": "https://api.dev.agentsync.io",
        "auth_url": "https://auth.dev.agentsync.io/oauth/token"
    },
    "test": {
        "api_base": "https://api.test.agentsync.io",
        "auth_url": "https://auth.test.agentsync.io/oauth/token"
    },
    "sandbox": {
        "api_base": "https://api.sandbox.agentsync.io",
        "auth_url": "https://auth.sandbox.agentsync.io/oauth/token"
    },
    "production": {
        "api_base": "https://api.agentsync.io",
        "auth_url": "https://auth.agentsync.io/oauth/token"
    }
}

def get_config(env_name=None):
    env = env_name or os.getenv("AGENTSYNC_ENV", "development")
    return ENVIRONMENTS[env]

Data Considerations

Data Isolation

  • Each environment has isolated data
  • Test data does not affect production
  • Credentials are environment-specific

Data Refresh

EnvironmentRefresh Schedule
DevelopmentWeekly (Sundays)
TestBi-weekly
SandboxMonthly or on request
ProductionN/A (live data)

Best Practices

Do

  • Use environment variables for configuration
  • Test in lower environments before production
  • Use separate credentials per environment
  • Coordinate load testing with DevOps
  • Monitor your API usage across environments

Don't

  • Use production credentials in development
  • Run destructive tests in Sandbox or Production
  • Assume data consistency across environments
  • Deploy directly to production without testing

Network Access

VPN Requirements

EnvironmentVPN Required
DevelopmentNo
TestNo
SandboxNo
ProductionNo
Internal APIsYes

Firewall Allowlist

If you need to allowlist our IPs, contact #devops-support for the current IP ranges.


Questions about environments? Contact #devops-support on Slack.