Orgnise’s API is currently in beta. If you have any questions or feedback, please reach out to us at orgnisehq@gmail.com.

​
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:
Terminal
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:
Terminal
Authorization: Bearer <Your-Token>
You can create a new token/API key under your Orgnise Account Settings.
API Key

​
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:
Terminal
https://api.orgnise.in/<Your-team-slug>
You can get your team slug either from team url or under your Orgnise team Settings.
Team Slug

​
Response Codes

The API returns standard HTTP response codes to indicate the success or failure of an API request. Here are a few examples:
CodeDescription
200The request was successful.
400The request was invalid or cannot be served.
401The request requires user authentication.
403The server understood the request, but refuses to authorize it.
404The requested resource could not be found.
429Too many requests.
500The 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.