Set Authentication

When several APIs share the same credentials, for example all the actions you imported from one OpenAPI schema, you can configure authentication once and apply it to all of them in a single step. This tutorial walks you through Set Authentication on the Custom API page, using the project APIs of Atlas, Kirana Group's operations assistant.

Before you start

• You have at least one API on the Custom API page, either added by hand (Connect Your API) or from a spec (Import an OpenAPI Schema). Atlas has get_project_status and list_projects.
• You have the credentials for those APIs: a token, a username and password, a custom header key, or OAuth details.
• You know how to test and publish changes. See Preview and Publish Changes.

About the sample API: the Kirana Projects API used in these tutorials is a public sample and does not accept credentials. If you send it a Bearer token, it answers 403. Kirana's real Projects API would require a Bearer token, which is the situation this page describes. If you follow along with the sample, click Cancel at the end of Step 3 instead of OK, or set the APIs back to None afterwards.

When to Use This Feature

Use Set Authentication when:

• You have just imported multiple APIs from an OpenAPI schema and need to add credentials to all of them at once
• Several existing APIs on your agent use the same token or username and password, and you need to rotate or update that credential
• You want to apply or remove authentication on a specific set of APIs without editing each one individually

Supported Authentication Types

Step 1: Open the Set Authentication Panel

On the Custom API page, click Set Authentication in the row of buttons at the top. The Set Authentication panel opens with the line "Configure an authentication once and apply it to multiple custom APIs at the same time."

Step 2: Configure the Authentication

In the Authentication section, choose the Auth Type that matches your API. The fields for that type appear next to it. For Kirana's Projects API, choose Bearer and paste the token into Key. The value is masked as you type.

Step 3: Select the APIs and Apply

Under Select APIs to update, tick the APIs that should get this authentication. APIs are grouped by category; APIs without a category are under Uncategorized. The header shows how many are selected, for example (1 selected).

• Select All ticks every API in the list.
• Clear All unticks every API.
• Select group / Clear group next to a category ticks or unticks all APIs in that category.

In the screenshot, get_project_status is ticked. For Atlas, tick list_projects as well, since both call the same API.

Click OK (it is disabled until at least one API is ticked). The CMS warns: "Authentication for 2 custom APIs will be changed. This will overwrite their current authentication configuration. Do you want to continue?" Click Yes.

Note: This overwrites the existing authentication on every selected API. APIs you do not select are left untouched.

Step 4: Save All Changes

The new authentication is only in the form so far. Click Save all changes at the bottom of the Custom API page. The CMS asks Are you sure to save your changes? Click Yes. A message confirms Custom API successfully updated!

The updated authentication is saved as a draft. It reaches real users after you click Publish in the top bar.

Check the result

1. In the list, the chip next to each updated API now shows the new auth type, for example Bearer instead of None.
2. Click one of the updated APIs, then Test API. The API Details show the new Authentication. Fill in a sample value, for example KG-2041, and click Call API. A 401 or 403 status usually means the credentials are wrong, or, with the public sample, that the API does not accept credentials at all.
3. In the preview panel, ask a question that should trigger one of the updated APIs, for example "What is the status of KG-2041?", and confirm that Atlas answers with real data.
4. Click Publish when everything works. See Preview and Publish Changes.

Authentication Details Reference

Bearer token

Basic authentication

Custom header

OAuth 2.0, Client Credentials

OAuth 2.0, Google Service Account

Next steps

• Next in the journey: Connect an MCP Server, to give your agent many tools from one server connection.
• Connect Your API: configure authentication for a single API action.
• Using Plugins: use pre-built integrations that handle authentication for you.