Introduction
Fundamental concepts of Tally’s API.
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:
Authentication
Authentication to the Tally API requires an Authorization header with a Bearer token. Include the Authorization header in your requests as shown below:
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 |
Rate Limits
To ensure fair usage and maintain service quality, the Tally API limits requests to 100 per minute.
Avoid rate limits with webhooks! Instead of polling for new form submissions, use webhooks to receive data instantly when forms are submitted. This is more efficient and won’t count against your rate limit.
Caveats
- Tally’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.