> For the complete documentation index, see [llms.txt](https://api-how-to.plannrcrm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-how-to.plannrcrm.com/readme.md).

# Welcome!

Introduction

Welcome to the Plannr API guide! Here you will find all the documentation you need to get up and running with Plannr API. Have fun!

## Get Started with Plannr

Before you start using the API, you will need to complete some necessary steps to get going. You'll also find useful links to help you as you consume our API. It is highly recommended to start here - you'll start at the very beginning by authorising yourself and end with making an example request to the API:

{% content-ref url="/pages/y6myHLmGygQAweJTprLc" %}
[Authentication](/getting-started/authorization.md)
{% endcontent-ref %}

## Want to deep dive?

Dive a little deeper and start exploring our API reference to get an idea of everything that's possible with the API:

[https://apidocs.plannrcrm.com](https://apidocs.plannrcrm.com/)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://api-how-to.plannrcrm.com/readme.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 `build a script that syncs our docs to a CMS` 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.