> 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/api/getting-started.md).

# Quick Start

## Authentication

All DCKAP Integrator API's needs to be authenticated using [bearer token](/api/getting-started.md#authentication-using-bearer-token) or access token.

### Authentication using Bearer Token

{% hint style="success" %}
This is the recommended approach.
{% endhint %}

As a first step, bearer token should be generated from the DCKAP Integrator account. Refer the below link to fetch the access token.

{% content-ref url="/pages/-MITXHRrdaOA-01X5770" %}
[API Access Keys](/user-guide/api-access-keys.md)
{% endcontent-ref %}

Once the token is generated, it should be passed in the API request headers like below. The *{generated\_access\_token}* should be replaced with your token.

```
{
    Authorization: Bearer {generated_access_token}
}
```

## Bearer Token Example

<mark style="color:blue;">`GET`</mark> `https://integrator.dckap.com/api/sample/url`

#### Headers

| Name          | Type   | Description                         |
| ------------- | ------ | ----------------------------------- |
| Authorization | string | Bearer {*generated\_access\_token}* |

{% tabs %}
{% tab title="200 Successfull Response" %}

```
{}
```

{% endtab %}

{% tab title="401 Authentication Error" %}

```
{}
```

{% endtab %}
{% endtabs %}


---

# 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/api/getting-started.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.