> For the complete documentation index, see [llms.txt](https://docs.tpi.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tpi.dev/digirunner-open-source/most-common-use-cases/enabling-apis-and-no-auth-in-batches-with-api-imported.md).

# Enabling APIs and No Auth in Batches with API Imported

The imported file must be a JSON file exported from digiRunner. This feature simplifies the process of handling multiple APIs with the same settings. If set to **No Auth**, it simplifies the authentication process, allowing for quick verification of API call success.

### Importing APIs to digiRunner <a href="#toc164347076" id="toc164347076"></a>

Application scenarios include the operation of launching APIs from the test environment to the official environment, the launching of multi-center APIM, or API migration.

1. Go to **API Management** > **API List**, and click **Import API**.

![](/files/OEypCMTCVjoNFzfBuiaK)

2. Click on the **File** icon, select the file, and then click **Upload**. A successful upload prompt will pop up, and the API information will be displayed in the table below.

![](/files/TiLw7l3NLTw1362oOoe6)

3. Check the list to select all APIs, and then click the **Import** button to import the APIs successfully. The import result will be updated to **success**.

![](/files/JZyZziVp96g9DwCaqM3p)

### Enabling APIs in Batches <a href="#toc164347077" id="toc164347077"></a>

1. Go to **API Management** > **API Modify** **Batch** to enter the page. The default statuses of the newly imported APIs will be displayed with a red icon, indicating that the API is not yet enabled.

![](/files/30GaurzAGN6n9gxDVaWm)

2. Check the box in the header cell to select all the APIs, and click **Enable**. A confirmation message will appear, click **Confirm** to save and exit.

![](/files/HIcy5NlhxvDWl9EyI05s)

3. A successful update prompt will pop up, and the status light will turn green, indicating that the API has been successfully enabled.

![](/files/Zqbdm6u0AzUrC0AqwGLP)

### Enabling No Auth for APIs in Batches <a href="#toc164347078" id="toc164347078"></a>

1. The default status of No Auth for newly imported APIs is disabled, and the field is empty.

![](/files/3EtIMAEWChGBdI3qIKDF)

2. Check the box in the header cell to select all the APIs, and click **Active No Auth**. A confirmation message will appear, click **Confirm** to save and exit.

![](/files/tcg0jplSoDLd3v2bhjAi)

3. A successful update prompt will pop up, and the No Auth field will display a check symbol, indicating that **No Auth** has been enabled.

![](/files/lTrtz2l8RNA401ZBzGRC)


---

# 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://docs.tpi.dev/digirunner-open-source/most-common-use-cases/enabling-apis-and-no-auth-in-batches-with-api-imported.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.
