> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orgnise.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Fundamental concepts of Orgnise's API.

<Info>
  Orgnise's API is currently in beta. If you have any questions or feedback,
  please reach out to us at
  [orgnisehq@gmail.com](mailto:orgnisehq@gmail.com?subject=Orgnise%20API%20Feedback).
</Info>

## Base URL

Orgnise's API is built on REST principles and is served over HTTPS. To ensure data privacy, unencrypted HTTP is not supported.

The Base URL for all API endpoints is:

```bash Terminal theme={null}
https://api.orgnise.in
```

## Authentication

Authentication to Orgnise's API is performed via the Authorization header with a Bearer token. To authenticate, you need to include the Authorization header with the word `Bearer` followed by your token in your API requests like so:

```bash Terminal theme={null}
Authorization: Bearer <Your-Token>
```

You can create a new token/API key under your [Orgnise Account Settings](https://app.orgnise.in/settings/tokens).

<Frame>
  <img className="" src="https://mintcdn.com/orgnise/4XUEaCZEjm10ZMTZ/images/introduction/apk-key-settings.png?fit=max&auto=format&n=4XUEaCZEjm10ZMTZ&q=85&s=7bff6281305fbfdd12d04305667b0252" alt="API Key" width="899" height="527" data-path="images/introduction/apk-key-settings.png" />
</Frame>

## Team Slug

Orgnise's API is organized around team. Each team has its own set of resources and permissions. To access a team's resources, you need to include the `team_slug` in your API requests like so:

```bash Terminal theme={null}
https://api.orgnise.in/<Your-team-slug>
```

You can get your team slug either from team url or under your Orgnise team Settings.

<Frame>
  <img className="" src="https://mintcdn.com/orgnise/4XUEaCZEjm10ZMTZ/images/introduction/team-slug.png?fit=max&auto=format&n=4XUEaCZEjm10ZMTZ&q=85&s=51db935fe233a46e04746bd3ce326ae5" alt="Team Slug" width="961" height="692" data-path="images/introduction/team-slug.png" />
</Frame>

## Response Codes

The API returns standard HTTP response codes to indicate the success or failure of an API request. Here are a few examples:

| Code  | Description                                                                                    |
| ----- | ---------------------------------------------------------------------------------------------- |
| `200` | The request was successful.                                                                    |
| `400` | The request was invalid or cannot be served.                                                   |
| `401` | The request requires user authentication.                                                      |
| `403` | The server understood the request, but refuses to authorize it.                                |
| `404` | The requested resource could not be found.                                                     |
| `429` | Too many requests.                                                                             |
| `500` | The server encountered an unexpected condition which prevented it from fulfilling the request. |

## Caveats

* Orgnise's API is currently in public beta and is subject to change. However, we will do our best to keep breaking changes to a minimum.