feishu-common

You can manage Feishu tenant tokens automatically by importing the fetch wrapper, which handles token caching and expiry refresh internally. It requires setting the FEISHU_APP_ID and FEISHU_APP_SECRET environment variables to authenticate requests.

Handle Feishu API rate limits using the built-in retry logic with exponential backoff. The fetch wrapper automatically detects 429 responses and retries the failed authenticated requests to ensure resilient API interactions.

No, you do not need to manually refresh expired Feishu tenant tokens. The module automatically caches tokens and handles refresh logic upon expiry, providing resilient authenticated API calls without manual intervention.

Feishu API authentication requires the FEISHU_APP_ID and FEISHU_APP_SECRET environment variables. These credentials allow the centralized token management system to generate, cache, and refresh tenant tokens for authenticated requests.

Your Feishu API wrapper likely fails on 429 errors because it lacks built-in rate limit handling. This module resolves 429 errors by implementing robust retry logic with exponential backoff to manage rate limits and ensure request completion.

The best way to centralize Feishu authentication is using a unified helper that manages tenant token caching, automatic refresh, and a lightweight fetch wrapper. This ensures consistent authentication and resilient retries across all Feishu API endpoints.