> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/project-manager/systems-builder/builder-credentials.md).

# Builder Credentials

The Builder Credentials tab allows System Builders to create credentials solely for testing APIs during the system creation process for each system version. It appears next to the System Details tab on the System Overview page and lists all added credentials. Builders can Add, Edit, Delete or Test credentials as needed.

## Adding a Credential

When you click “Add Credential,” a pop-up appears where you can enter test credential details. The form fields change depending on the selected authentication type (e.g., Basic, OAuth1, OAuth2, Token, etc.).

### **Credential Fields (Basic Auth Example)**&#x20;

* **Credential Name** (required):\
  A unique and recognizable name for the credential.
* **Timezone**:\
  Select the timezone relevant to the credential (affects time-based API testing).
* **Username** (required):\
  Username for authentication.
* **Password** (required):\
  Password for authentication (eye icon available to toggle visibility).

{% hint style="info" %}
Field options adjust automatically based on the selected authentication type. Any fields added under the Credential Inputs section will also appear when adding or editing a credential.
{% endhint %}

## Testing and Saving

Click “Test and Save” to validate the credential. Only valid credentials will be saved. If Test Connection fails due to invalid credentials, the save will be blocked and an error log will appear.

## Testing Existing Credentials

Use the “Test Connection” button to verify if an added credential is working properly with the system.

## Important Notes

* Only one builder credential per authentication type is allowed per system version.
* Each credential is tied to a specific version of the system (including drafts).
* Only one authentication type is supported per system in the initial release.
* This tab is visible only to System Builders - end users cannot access it.
* This feature is meant for building systems and testing APIs before use.


---

# 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://docs.dckapintegrator.com/project-manager/systems-builder/builder-credentials.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.
