ACME maintains and allows access to multiple sandbox environments to help facilitate on-boarding, upcoming release previews, configuration testing, API integration development, troubleshooting and more! These environments provide our clients with a place to experiment without impacting their production environments.

Access

When accessing any sandbox a user will encounter a system authentication check. When logging into a sandbox a pop up window will open that looks like this:

The username and password credentials are the same for everyone. Use the following to complete the authentication check:


User Name: pilot_user
Password: tinTin15

Sandbox 1 - Onboarding

The Onboarding Sandbox, or Sand1, is the place where all new clients complete their initial configuration and training. Once satisfied with the configuration, the tenant is built and finalized in the Production Environment and Sand1 is abandoned.

Code Refresh Interval

Code is in sync with Production Code

Data Refresh Interval

Never (Stable)

Backoffice URL

https://sand1-backoffice.acmeticketing.net/login

Online Ticketing URL

https://sand1-buy.acmeticketing.net/events/###/list*

API Base URL

https://sand1-api.acmeticketing.net/

* Replace the ### in the link with your Tenant ID. Note that this will be different than your Production Tenant ID. 

Sandbox 10 - Preview

Sandbox 10 is where we release code before it’s available in production. Approximately two weeks before a release, you’ll be able to test new features, functionality, enhancements, and bug fixes in preparation for the push to production.  

You can also use this sandbox to test out new configurations or unimplemented features that you may be considering using in your venue.  

Code Refresh Interval

Code is one version ahead of Production Code

Data Refresh Interval

Approximately every 4 releases (Unstable)

Backoffice URL

https://sand10-backoffice.acmeticketing.net/login

Online Ticketing URL

https://sand10-buy.acmeticketing.net/events/###/list*

API Base URL

https://sand10-api.acmeticketing.net/

* Replace the ### in the link with your Tenant ID

Sandbox 15 - Project Box

Project Sandboxes are for users who are working on longer-term projects that require a bit more stability when it comes to data refreshes. Generally, these sandboxes are used for API integrations and major feature implementations. Before using a Project Sandbox, please contact api-help@acmeticketing.com for guidance on which sandbox to use.

Code Refresh Interval

Code is in sync with Production Code

Data Refresh Interval

Approximately every 4 months (Semi-Stable)

Backoffice URL

https://sand15-backoffice.acmeticketing.net/login

Online Ticketing URL

https://sand15-buy.acmeticketing.net/events/###/list*

API Base URL

https://sand15-api.acmeticketing.net/

* Replace the ### in the link with your Tenant ID

Sandbox Code and Data Refreshes

In order to maintain consistency between the ACME Sandboxes and the ACME Production environments, we frequently update both the code and the data in the sandboxes to support their intended uses.

Code Refreshes

With the exception of Sandbox 10, the code in the ACME Sandboxes is generally in sync with Production. This provides sandboxes users with an environment that is close as possible to the production environment.

Data Refreshes

To ensure the sandboxes have similar configuration and transaction data like production, we periodically overwrite sandbox data with production data. This means that, when a data refresh occurs, anything you have in a sandbox that is not also in production will be destroyed.

Note

When a data refresh occurs, be sure to check your sandbox payment processor settings in Back Office Settings>Administration>Payments. A data refresh will cause your test card payment settings to be replaced with your production card processor, causing test cards to fail. 

  • If you wish to test the WorldPay Express test card numbers, set the payment processor to Express and enter your testing credentials in Back Office
  • For all other testing use cases, change the payment processor to Stripe to use the ACME supplied test card numbers


Past Importer/Exporter job files may not be available in ACME Sandboxes. To retrieve historical job files, please use the Production environment.

Before beginning any longer-term project in a sandbox, please contact api-help@acmeticketing.com so we can assign you a sandbox that is the best fit for your project.


Important: Because the sandboxes are shared, we cannot delay any planned data or code refreshes on any of the sandboxes.


Sandbox Code and Data Refresh Schedule

The data refresh schedule for our sandbox environments is now posted in our Community Forum.