Lattice Sandboxes

Setting up an environment in Lattice Sandboxes

Lattice Sandboxes

Setting up an environment in Lattice Sandboxes

Lattice Sandboxes is a secure, isolated platform for creating environments with simulated data to develop and test your Lattice SDK app. Apps developed on Sandboxes are portable and can be used in other Lattice deployments based on your environment requirements.

Pricing

Lattice Sandboxes environments are provided free of charge. You can make an unlimited number of free API calls to your environment to create, stream, and task entities in Lattice.

Before you begin

If you don’t have access to Lattice Sandboxes, request to join the Lattice SDK developer program.

Anduril uses Okta to authenticate access to Lattice Sandboxes. Multi-factor authentication (MFA) is satisfied with a passkey, such as a browser passkey, operating system biometrics, or a physical FIDO/UBI security key.

Browser support

Use Chrome or a Chromium-based browser, such as Microsoft Edge or Brave, to access the Lattice Sandboxes developer portal. Firefox is not supported and will prevent you from completing the sign-in procedure.

If this is your first time signing in, activate your Okta account and register a passkey:

1Open the welcome email and choose the Activate Okta Account link. The link expires seven days after the email is sent.

2On the Set up security methods page, next to Password, choose Set up, then choose and confirm a password.

Next to Security Key or Biometric Authenticator, choose Set up, then register one of the following passkey options:

Browser passkey — Stored by your browser’s password manager so that you can sign in from any device signed in to the same browser profile.
Operating system biometrics — Uses Touch ID, Face ID, Windows Hello, or another built-in platform authenticator bound to the current device.
Physical FIDO or UBI key — Uses a hardware token such as a YubiKey, which you can carry with you between devices.

To sign in after activation, do the following:

1Open the Lattice Sandboxes sign-in page.

2For Username, enter the email address that you used to request access to the Lattice Developer program.

3For Password, enter the password you created during activation.

4Complete the passkey challenge using the authenticator method you registered. On success, Okta redirects you to the Lattice Sandboxes dashboard.

To manage your passkeys and password, visit https://login.developer.anduril.com/account-settings/home. If you lose access to your passkey, reach out to lattice-developers@anduril.com for assistance.

After logging in, the dashboard displays all existing environments associated with your account and the status of each environment.

Create an environment

To create a new environment, open the Environment Catalog, the do the following:

Choose New Environment.

On the Environment Catalog page, choose Lattice and click Create. You’ll be redirected to the environment creation details page, where you see the status of your environment:

Once the state changes to Ready, review the following details:

Resource Endpoint

Use this to launch the Lattice UI or connect to Lattice programmatically.

Lattice Client ID

Use the client ID to authorize your integration with the Lattice SDK.

Lattice Client Secret

Use the client secret to authenticate your integration with the Lattice SDK.

Lattice User

The user name you use to log in to the Lattice UI.

Lattice Password

The password you use to log in to the Lattice UI.

Lattice Auth Token

This is your environment token. Save this token in addition to the Sandboxes token, to authenticate your requests with the Lattice API.

Confirm you have access to your environment by clicking the Lattice URL link, then log in using the provided user name and password.

Restrictions

Create up to 2 concurrent environments in Sandboxes.
Environments have a maximum lifetime of 12 hours.
Environments have a maximum idle lifetime of 2 hours. You must make a network call, or sign in to the Lattice UI to keep your environment active.
Access tokens obtained using client credentials have a lifetime of 30 minutes.

Set up credentials

To query your Sandboxes environment, you will need:

Sandboxes token (anduril-sandbox-authorization header) — This is your account-level authorization token. Create this token once, then use it to access all of your environments.
Lattice Client ID — This is the credential your integration will use for authorization with the environment. The Client ID is automatically generated when creating a new environment.
Lattice Client Secret — This is the credential your integration will use for authentication with the environment. The Client Secret is automatically generated when creating a new environment.

All credentials are required at runtime to interact with Lattice Sandboxes. The Sandboxes Proxy verifies your Sandboxes token, then forwards the request to your environment.

Diagram showing the authorization flow for Lattice Sandboxes.

To create a new Sandboxes token, do the following:

1Open the Account & Security page in Sandboxes portal, not the Lattice environment. This token can be used for all environments for the life of the token.

In the Bearer tokens section, click + New Token:

Shows the Account & Security page where you can create, and manage, your
authorization tokens.

On the Create Bearer Token modal, enter the following:

Bearer token name — Enter a descriptive name for your Sandboxes token.
Bearer token expiration — Select an expiration time frame.

Click Create to generate a Sandboxes token, then save your Sandboxes token.

After this step, the Sandboxes token will not be visible again.

To authenticate API requests to your Sandboxes environment, you will need to obtain an access token using the Lattice Client ID and Lattice Client Secret.

If your environment page doesn’t display a Lattice Client ID or Lattice Client Secret, under “Resource Credentials”, contact your Anduril representative.

Send a POST request with the client_id and client_secret to the /api/v1/oauth/token endpoint.

curl --request POST "https://$LATTICE_ENDPOINT/api/v1/oauth/token" \
        --header "Anduril-Sandbox-Authorization: Bearer $SANDBOXES_TOKEN" \
        --header "Content-Type: application/x-www-form-urlencoded" \
        --data-urlencode "grant_type=client_credentials" \
        --data-urlencode "client_id=$LATTICE_CLIENT_ID" \
        --data-urlencode "client_secret=$LATTICE_CLIENT_SECRET"

If the request is sucessful, you will receive a 200 status response. The body will contain the following data:

1 {
2     "access_token" : "*****",
3     "expires_in" : 1800,        // seconds
4     "scope": "lattice"
5 }

Export the access_token as an environment variable.

export ENVIRONMENT_TOKEN="*****"

You can now use the access_token as the Authorization token to interact with Lattice.

curl -X GET https://$LATTICE_ENDPOINT/api/v1/objects \
     -H "Authorization: Bearer $ENVIRONMENT_TOKEN" \
     -H "Anduril-Sandbox-Authorization: Bearer $SANDBOXES_TOKEN"

Token refresh

The access_token returned will only be valid for the value of expires_in, in seconds. If you’re accessing the SDK through the REST clients, the clients will automatically manage refresh for you. If you are interacting with the SDK using gRPC or cURL, you will have to manage the token refresh based on the expires_in property.

What’s next?

Test your new environment by running the Quickstart guide.
Install the Lattice SDK for a protocol and language of your choice to get started developing with Lattice.

Pricing

Lattice Sandboxes environments are provided free of charge. You can make an unlimited number of free API calls to your environment to create, stream, and task entities in Lattice.

Before you begin

If you don’t have access to Lattice Sandboxes, request to join the Lattice SDK developer program.

Browser support

If this is your first time signing in, activate your Okta account and register a passkey:

1Open the welcome email and choose the Activate Okta Account link. The link expires seven days after the email is sent.

2On the Set up security methods page, next to Password, choose Set up, then choose and confirm a password.

Next to Security Key or Biometric Authenticator, choose Set up, then register one of the following passkey options:

Browser passkey — Stored by your browser’s password manager so that you can sign in from any device signed in to the same browser profile.
Operating system biometrics — Uses Touch ID, Face ID, Windows Hello, or another built-in platform authenticator bound to the current device.
Physical FIDO or UBI key — Uses a hardware token such as a YubiKey, which you can carry with you between devices.

To sign in after activation, do the following:

1Open the Lattice Sandboxes sign-in page.

2For Username, enter the email address that you used to request access to the Lattice Developer program.

3For Password, enter the password you created during activation.

4Complete the passkey challenge using the authenticator method you registered. On success, Okta redirects you to the Lattice Sandboxes dashboard.

After logging in, the dashboard displays all existing environments associated with your account and the status of each environment.

Create an environment

To create a new environment, open the Environment Catalog, the do the following:

Choose New Environment.

On the Environment Catalog page, choose Lattice and click Create. You’ll be redirected to the environment creation details page, where you see the status of your environment:

Once the state changes to Ready, review the following details:

Resource Endpoint

Use this to launch the Lattice UI or connect to Lattice programmatically.

Lattice Client ID

Use the client ID to authorize your integration with the Lattice SDK.

Lattice Client Secret

Use the client secret to authenticate your integration with the Lattice SDK.

Lattice User

The user name you use to log in to the Lattice UI.

Lattice Password

The password you use to log in to the Lattice UI.

Lattice Auth Token

This is your environment token. Save this token in addition to the Sandboxes token, to authenticate your requests with the Lattice API.

Confirm you have access to your environment by clicking the Lattice URL link, then log in using the provided user name and password.

Restrictions

Create up to 2 concurrent environments in Sandboxes.
Environments have a maximum lifetime of 12 hours.
Environments have a maximum idle lifetime of 2 hours. You must make a network call, or sign in to the Lattice UI to keep your environment active.
Access tokens obtained using client credentials have a lifetime of 30 minutes.

Set up credentials

To query your Sandboxes environment, you will need:

Sandboxes token (anduril-sandbox-authorization header) — This is your account-level authorization token. Create this token once, then use it to access all of your environments.
Lattice Client ID — This is the credential your integration will use for authorization with the environment. The Client ID is automatically generated when creating a new environment.
Lattice Client Secret — This is the credential your integration will use for authentication with the environment. The Client Secret is automatically generated when creating a new environment.

All credentials are required at runtime to interact with Lattice Sandboxes. The Sandboxes Proxy verifies your Sandboxes token, then forwards the request to your environment.

To create a new Sandboxes token, do the following:

1Open the Account & Security page in Sandboxes portal, not the Lattice environment. This token can be used for all environments for the life of the token.

In the Bearer tokens section, click + New Token:

On the Create Bearer Token modal, enter the following:

Bearer token name — Enter a descriptive name for your Sandboxes token.
Bearer token expiration — Select an expiration time frame.

Click Create to generate a Sandboxes token, then save your Sandboxes token.

After this step, the Sandboxes token will not be visible again.

To authenticate API requests to your Sandboxes environment, you will need to obtain an access token using the Lattice Client ID and Lattice Client Secret.

If your environment page doesn’t display a Lattice Client ID or Lattice Client Secret, under “Resource Credentials”, contact your Anduril representative.

Send a POST request with the client_id and client_secret to the /api/v1/oauth/token endpoint.

curl --request POST "https://$LATTICE_ENDPOINT/api/v1/oauth/token" \
        --header "Anduril-Sandbox-Authorization: Bearer $SANDBOXES_TOKEN" \
        --header "Content-Type: application/x-www-form-urlencoded" \
        --data-urlencode "grant_type=client_credentials" \
        --data-urlencode "client_id=$LATTICE_CLIENT_ID" \
        --data-urlencode "client_secret=$LATTICE_CLIENT_SECRET"

If the request is sucessful, you will receive a 200 status response. The body will contain the following data:

1 {
2     "access_token" : "*****",
3     "expires_in" : 1800,        // seconds
4     "scope": "lattice"
5 }

Export the access_token as an environment variable.

export ENVIRONMENT_TOKEN="*****"

You can now use the access_token as the Authorization token to interact with Lattice.

curl -X GET https://$LATTICE_ENDPOINT/api/v1/objects \
     -H "Authorization: Bearer $ENVIRONMENT_TOKEN" \
     -H "Anduril-Sandbox-Authorization: Bearer $SANDBOXES_TOKEN"

Token refresh

What’s next?

Test your new environment by running the Quickstart guide.
Install the Lattice SDK for a protocol and language of your choice to get started developing with Lattice.

1	{
2	"access_token" : "*****",
3	"expires_in" : 1800, // seconds
4	"scope": "lattice"
5	}

Pricing

Before you begin

Sign in

Browser support

Create an environment

Restrictions

Set up credentials

Token refresh

What’s next?

Pricing

Before you begin

Sign in

Browser support

Create an environment

Restrictions

Set up credentials

Token refresh

What’s next?