> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/software/basespace-cli/software-basespace-cli-reference_material-list/000005560.md).

# How to authenticate BaseSpace CLI to another region or Enterprise domain

There are multiple instances of BaseSpace to serve different regions around the world. These instances are housed in separate data centers and have different base URLs for the API. The default API URL when using the `bs authenticate` command is: <https://api.basespace.illumina.com>, which is the USE1 region based in Virginia, USA.

The current list of instances and their respective API URLs are available in the [BaseSpace Sequence Hub Help Center](https://help.basespace.illumina.com/manage-your-account/regions).

To authenticate on an instance other than USE1 the `--api-server` option must be used in conjunction with the appropriate API URL. For example, to authenticate to EUC1, the following command can be used:

```
bs auth --api-server https://api.euc1.sh.basespace.illumina.com  
```

**Note**: The `--api-server` must be used when authenticating to a non-USE1 instance (for Personal (Basic) accounts **and** Professional or Enterprise workgroups). When authenticating to a Professional or Enterprise workgroup (on USE1), the `--api-server` option is not needed, and users can authenticate the same way they would for a Personal account.

More information on authentication options can be found in the [BaseSpace CLI documentation](https://developer.basespace.illumina.com/docs/content/documentation/cli/cli-overview#Authenticateanameauthenticatea).

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                 |
| :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #5560), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000005560%20-%20Software%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.illumina.com/software/basespace-cli/software-basespace-cli-reference_material-list/000005560.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
