API Documentation
Introduction
Fundamental concepts of Tally’s API.
Tally’s public API is currently in beta and subject to change.
Base URL
The Tally API follows REST principles and is accessible only via HTTPS. For security reasons, unencrypted HTTP requests are not allowed. The Base URL for all API endpoints is:
Terminal
Authentication
Authentication to the Tally API requires an Authorization header with a Bearer token. Include the Authorization header in your requests as shown below:
Terminal
Learn more about how to get your API key.
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 | Success - The request completed successfully |
400 | Bad Request - The request was malformed or contained invalid parameters |
401 | Unauthorized - Authentication credentials are missing or invalid |
403 | Forbidden - You don’t have permission to access this resource |
404 | Not Found - The requested resource doesn’t exist |
429 | Rate Limited - You’ve exceeded the allowed number of requests |
500 | Server Error - Something went wrong on our end |
Caveats
- Tally’s public API is currently in beta and is subject to change. However, we will do our best to keep breaking changes to a minimum.