> 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/organization.md).

# Organization

Read the organization behind your access token, including the plans it can put a client workspace on.

Your token identifies one organization, so this endpoint takes no id: it always reads as the organization the token belongs to. Its `id` is the uuid Kick holds for your firm, and `name` is the firm name shown in the product.

`allowedPlans` is the set of plans your organization can put a client workspace on, and it is exactly what `plan` accepts on [workspace create and update](/api/api-reference/workspaces.md). Reading it is how an integration learns which values a request may send, instead of discovering a rejected plan as a `400`.

## Retrieve the organization

> Returns the organization behind the access token: its id, name and the plans it may assign to a client workspace.

```json
{"openapi":"3.0.2","info":{"title":"Kick Platform API","version":"v1"},"servers":[{"description":"Production","url":"https://use.kick.co/api"}],"security":[{"organizationAccessToken":[]}],"components":{"securitySchemes":{"organizationAccessToken":{"description":"Organization access token issued by Kick, sent as `Authorization: Bearer kick_org_...`.","scheme":"bearer","type":"http"}}},"paths":{"/platform/v1/organization":{"get":{"description":"Returns the organization behind the access token: its id, name and the plans it may assign to a client workspace.","operationId":"organization.get","parameters":[],"responses":{"200":{"content":{"application/json":{"schema":{"properties":{"organization":{"properties":{"allowedPlans":{"items":{"enum":["FREE","BASIC","PLUS","ADVANCED","READ_ONLY","TAX"],"type":"string"},"type":"array"},"id":{"format":"uuid","type":"string"},"name":{"type":"string"}},"required":["id","name","allowedPlans"],"type":"object"}},"required":["organization"],"type":"object"}}},"description":"200"},"401":{"content":{"application/json":{"schema":{"properties":{"message":{"type":"string"},"traceId":{"nullable":true,"type":"string"}},"required":["message"],"type":"object"}}},"description":"401"},"429":{"content":{"application/json":{"schema":{"properties":{"message":{"type":"string"},"traceId":{"nullable":true,"type":"string"}},"required":["message"],"type":"object"}}},"description":"429"}},"summary":"Retrieve the organization","tags":["organization"]}}}}
```


---

# 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/organization.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.