ACME maintains and allows access to multiple sandbox environments to help facilitate onboarding, 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.



When accessing any sandbox a user will first encounter a system authentication check. When logging into a sandbox environment, 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

The login page to ACME's Backoffice application will appear. This is where you enter your email address and password.

Note: For security, only users with your institution's email domain can receive emails issued from Sandbox environment or be invited to it. If you need to invite users with a new or different email domain, you will need to email requesting that the new domain be safelisted, which must be completed before you can issue an invite for users at that domain.

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 train new users, and 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 2 months (Unstable)

Backoffice URL

Online Ticketing URL*


* 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 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

Online Ticketing URL*


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

Testing in a Sandbox Environment

When a data refresh occurs, there is no longer any need to change your payment processor settings in Backoffice Settings>Administration, Payment tab. When testing, please use the ACME Credit Cards for Sandbox Testing, which will work in any sandbox environment. 

For security, emails triggered in a Sandbox environment are only sent safelisted domains. This is to ensure that a real guest doesn't get an email that looks like actual tickets or a membership, when it is actually a test purchase. Please ensure you are using your institution's email for any tests if you need to see the email that is issued.

To ensure improved deliverability of emails to your customers, we complete an authorization process for the email domain used for sending ACME generated emails in Production. This authorization does not apply to the test environments, which results in test emails ending up in your Spam folder. 

Tip: You can update the "from" email address variables to use in a test environment to improve deliverability of test emails.

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. With the exception of Sandbox 10 during release preview periods, 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.

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 so we can assign you a sandbox that is the best fit for your project.

If you are using our Salesforce integration, you may want to do a synced refresh of your Salesforce data at the same time as ACME, to ensure IDs for Prod data are present and aligned across both systems. If you choose to do a synced refresh, the cadence is as follows:

  1. On the day of the refresh, ACME will halt the Sand10/SF test integration in preparation for the data refresh
  2. On the day of the refresh at 20:44 UTC, ACME starts copying ACME Prod data
  3. On the day of the refresh at 20:44 UTC, Client starts the SF Prod copy to their test SF environment
  4. When the data copy in step 2 is completed, ACME loads the ACME Prod copy into Sand10 (either late the same day or early the next day)
  5. After the SF copy has completed, Client updates the ACME integration user in the SF test environment to a valid email address and confirms all permissions have been activated to allow ACME to restart the integration, and informs ACME when this is done
  6. When that is complete, ACME restarts the Sand10/SF test integration (timing depending on the above steps)

Important: Since sandboxes are a multi-tenant environment, we cannot delay any planned data or code refreshes. Please plan accordingly!

Sandbox Code and Data Refresh Schedule

The data refresh schedule for our sandbox environments is now posted on our Current System Versions and Status page and in our Community Forum.