Tropo operates multiple environments. For most customers, you know these as Development and Production. The developer environment runs the latest Tropo code, allowing you to test your applications against our newest builds before they run in production. The Production environment requires that billing be set up, and has considerably more capacity and none of the limitations of the Development environment. Moving an application from Development to Production can be accomplished by the push of a button in the Application Console, or via an API call to our Applications API. For most customers, the document Moving to Production describes the entire process of setting up billing and moving an application into production.
Enterprise customers may have multiple environments configured. In addition to Production, they may have a specialized production environment that isolates their applications and systems from others. Or is connected to private networks for security and performance. Or even a development environment for early access to new features. If you have multiple production environments available to you, your Application Console will list each environment and allow you to move an application between them.
To manage your application environment via an API, the Environments API can be used to determine which Environments you have access to. If you have not yet set up billing or signed an Enterprise agreement, only development environments will appear in the Environments API. To change an application to another environment, send a PUT request to the Applications API with the new Environment ID,
Applications that are running in a billing-enabled environment (i.e. Production) can only be moved to other billing-enabled environments. Applications that are in a Development environment can be moved to other development environments or to a billing-enabled environment.