# Authentication & Keys

This is intentional, so you can experience the integration in a **production-like environment** and see exactly how real-world transactions behave.

> Note: Keep your API Key secure. Do not expose it in client-side code or version control.

### 🛠️ Making Requests

All API requests to Kazza must include the following headers:

```
X-API-KEY: <API_KEY>
X-Account-ID: <ACCOUNT_ID>

```

**Base URL**

```
https://www.mykazza.api.business.com
```

<figure><img src="https://1101864857-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9CZ5FNsHt52PuK4kg7tr%2Fuploads%2FJBKaSy6ScmM7gubS6bOT%2FAccounts.png?alt=media&#x26;token=1055c7bc-8699-4747-b36c-23cb808fa193" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
See the screenshot above for how to navigate to the settings screen on your dashboard. From here, you can access your API credentials.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://developer.mykazza.com/getting-started/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.