> For the complete documentation index, see [llms.txt](https://legacy-docs.usesmileid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.usesmileid.com/integration-options/mobile/android/submit-a-job/environments.md).

# Environments (Deprecated)

There are two environments on Smile ID. Test which is used for development and Production which should be used for live deployments

### LIVE AND TEST

```
AUTH_URL = "api/v2/#/auth_smile/";
PARTNER_PORT = "8080";
SID_ADDRESS = "smileidentity";
SID_PORT = "8443";
```

### TEST

```
//Partner URL
PARTNER_URL = "https://portal.smileidentity.com/"

//LAMBDA URL
LAMBDA_URL = "https://testapi.smileidentity.com/v1/"
```

### PRODUCTION

```
//Partner URL
PARTNER_URL = "https://prod.smileidentity.com/"

//LAMBDA URL
LAMBDA_URL = "https://api.smileidentity.com/v1/"
```

### CALLBACK URL

From version 6.4.2 there is added functionality to set custom callback using the SDK, this can be done by using the SIDNetData class. After setting the other settings in this class then call the method`setCallBackUrl` as in the example below

If the call back URL is not set from the SDK it will always default to the setting on the backend.

More information on callback URL can be found [here](https://docs.smileidentity.com/results/callbacks)

```
SIDNetData data = new SIDNetData();
....//other SIDNetData settings
data.setCallBackUrl(https://example.com/callback);
```

### SETTING ENVIRONMENTS

```
SIDNetData data = new SIDNetData();
data.setAuthUrl(AUTH_URL);
data.setPartnerUrl(PARTNER_URL);
data.setPartnerPort(PARTNER_PORT);
data.setLambdaUrl(LAMBDA_URL);
data.setSidAddress(SID_ADDRESS);
data.setSidPort(SID_PORT);
data.setCallBackUrl(https://example.com/callback);

SIDConfig.Builder builder = new SIDConfig.Builder(this);
....
builder.setSmileIdNetData(data)
....
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://legacy-docs.usesmileid.com/integration-options/mobile/android/submit-a-job/environments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.