Note: This page is for internal Ensign development and will probably not be very useful to Ensign users. The staging environment has the latest code deployed frequently, may introduce breaking changes, and has it’s data routinely deleted.

Staging Environment #

Ensign developers can access the staging environment in order to perform testing and development or to QA release candidates before they are deployed.

To get started, make sure that you’ve created an API Key in the staging environment using the Beacon UI at Once you’ve obtained those credentials, add the following environment variables so that your script can access the credentials:


If you’re working on the Go SDK in staging, make sure you have the latest version from the commit rather than the latest tagged version so that your client code is up to date with what is in staging:

$ go get

By default the Ensign client connects to the Ensign production environment. To connect to Staging you need to specify the staging endpoints in your credentials:

client, err := ensign.New(&ensign.Options{
    Endpoint: "",
    ClientID: os.GetEnv("ENSIGN_CLIENT_ID"),
    ClientSecret: os.GetEnv("ENSIGN_CLIENT_SECRET"),
    AuthURL: "",

If you’re feeling extra, you can also use the endpoint which is an alias for