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

# Kizen API Reference

Explore Kizen’s API reference to create, query, and sync data, trigger workflows, build event-driven integrations, and extend the platform.

The <code class="expression">space.vars.Kizen\_company\_name</code> API Reference provides developers and technical builders with the tools needed to integrate, automate, and extend <code class="expression">space.vars.Kizen\_company\_name</code> programmatically. Use these APIs to work with data, schedule and log activities, trigger workflows, and build reliable integrations across systems.

***

## Getting Started

If you’re new to the <code class="expression">space.vars.Kizen\_company\_name</code> APIs, start here:

1. Understand the [data model](/docs/concepts/objects.md)
2. Learn about [authentication](/docs/developers/authentication.md)
3. Test the endpoints using [Swagger](https://app.go.kizen.com/api/docs/published/swagger)
4. Choose the right integration pattern
   * Use APIs for on-demand or batch operations, and Webhooks for near-real-time event handling.
   * SmartConnectors are a great way to load or sync large amounts of data on an ongoing basis

Whether you’re building a one-way data sync or a complex, multi-system workflow, the API Reference provides the technical detail needed to implement it correctly.

You can also check our existing API documentation topics for more information about using the APIs:

* [Activities API & Webhooks](/docs/concepts/activities/activities-api-and-webhooks.md)


---

# 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://developer.kizen.com/api/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 `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.