TagMango DocsRate Limiting
API rate limits and best practices
The TagMango API enforces rate limits to ensure fair usage and platform stability.
Limits
| Rate Limit | Window |
|---|---|
| 120 requests | Per 10 seconds |
When Rate Limited
You'll receive a 429 Too Many Requests response:
{
"statusCode": 429,
"message": "Too many requests, please try again later",
"success": false
}Best Practices
- Cache responses where possible
- Use webhooks instead of polling
- Implement exponential backoff on retries
- Spread requests evenly instead of bursting
Error Codes
API error codes and how to handle them
Get Authenticated User By Token GET
## Overview This endpoint is used to get the basic user details by JWT token. Its crucial for closely integrating your application with TagMango Dashboard. TagMango doesn't provide independent login solution to custom applications, in that case you can use this endpoint to get the user details by JWT token. TagMango will include JWT token(refresh token) of the current logged in user as a query parameter to the registered domain of the application. When user clicks on the custom application from the dashboard navigation menu, it will redirect to the registered domain of the application with this token as a query parameter. ## Query Parameters Example `https://your-app.domain.com?refreshToken={your-refresh-token}` Then you can extract the refresh token from the query parameter and use it to get the user details by calling this endpoint. You can also add other query parameters to the URL while adding your application in the dashboard (Settings -> Platform Settings -> Customise Menu).