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

# API Reference

- [Organization](https://docs.kick.co/api/api-reference/organization.md): Read the organization behind your access token, including the plans it can put a client workspace on.
- [Users](https://docs.kick.co/api/api-reference/users.md): List the members of your organization with their organization role and the date each one joined.
- [Workspaces](https://docs.kick.co/api/api-reference/workspaces.md): List and create the workspaces in your organization's book of business, and read, update, or delete a single workspace.
- [Entities](https://docs.kick.co/api/api-reference/entities.md): List and create the entities of a workspace, and read, update, or delete a single entity.
- [Chart of Accounts](https://docs.kick.co/api/api-reference/chart-of-accounts.md): Read an entity's chart of accounts, create, rename, archive, restore, merge, or delete its accounts, prepare categorization, and organize account groups.
- [Opening Balances](https://docs.kick.co/api/api-reference/opening-balances.md): Read, set, and delete the opening balances and bookkeeping start adjustments of the accounts in an entity's chart of accounts.
- [Plaid Connections](https://docs.kick.co/api/api-reference/plaid-connections.md): Open a bank connection from a Plaid processor token, list the connections your integration created, and delete one.
- [Financial Accounts](https://docs.kick.co/api/api-reference/financial-accounts.md): List a workspace's financial accounts and their sync health, then rename one, change its bookkeeping dates, move it to another entity, or delete it.
- [Transactions](https://docs.kick.co/api/api-reference/transactions.md): Read a workspace's transactions across all of its entities, read a single transaction, and update one.
- [Transaction Rules](https://docs.kick.co/api/api-reference/transaction-rules.md): List, create, update, and delete the transaction rules of a workspace, and read a single rule.
- [Classes](https://docs.kick.co/api/api-reference/classes.md): List, create, rename, and delete the classes of a workspace, and read a single class.
- [Tasks](https://docs.kick.co/api/api-reference/tasks.md): List and read the tasks and task groups of a client workspace, read a task's message thread, and post messages to it.
- [Ledgers](https://docs.kick.co/api/api-reference/ledgers.md): Open an entity's accrual ledger so you can post to it and report on it.
- [Journal Entries](https://docs.kick.co/api/api-reference/journal-entries.md): Read, write, update, and delete the manual journal entries of an entity's ledger.
- [Locks](https://docs.kick.co/api/api-reference/locks.md): Read and set the lock dates that close the books of the entities in your client workspaces.
- [Accounting Migration](https://docs.kick.co/api/api-reference/accounting-migration.md): Start an entity's accounting migration, check its status, and generate transaction rules from the migrated history.
- [Reports](https://docs.kick.co/api/api-reference/reports.md): Pull an entity's profit and loss, balance sheet, cash flow, trial balance, and general ledger.


---

# 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.kick.co/api/api-reference.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.