> For the complete documentation index, see [llms.txt](https://docs.zencal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zencal.io/quick-start.md).

# Quick Start

{% hint style="info" %}
**Good to know:** A quick start guide can be good to help folks get up and running with your API in a few steps. Some people prefer diving in with the basics rather than meticulously reading every page of documentation!
{% endhint %}

## Get your API keys

In order to obtain an API key, you must first have a registered and active account with Zencal. To do this, go to the [registration form](https://app.zencal.io/auth/register) and then go through the entire onboarding process.

If you already have a Zencal account, send a request for API keys to <hello@zencal.io>. It is important that the message is sent from the email to which the request relates. In addition, in the body of the email, provide the secret service code, which can be found in the Account tab of the Zencal dashboard.

## How to authorize yourself

To authorize yourself in the Zencal API, you need to use the `X-Zencal-Api-Key` header for this purpose. Set it to the value of the API key you obtained when you contacted us.&#x20;

Also set the `content-type` and `accept` headers to `application/json`

Now you are ready to call the Zencal API methods


---

# 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.zencal.io/quick-start.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.