Package selection guidance compiled from public package information, community data, and project usage.
Fresh Dio is a lightweight HTTP interceptor built on top of Dio that automates token refresh during API requests. It handles authentication tokens transparently, ensuring secure and uninterrupted access to protected endpoints. By intercepting requests and refreshing expired tokens seamlessly, it reduces boilerplate code and improves user experience. Ideal for apps requiring robust authentication workflows with minimal setup.
Use cases
Automatic token refresh during API calls
Handling expired JWT tokens
Securing authenticated API endpoints
Reducing manual token management
Improving login session persistence
Simplifying auth state handling
Key features
Built on top of Dio
Transparent token refresh
Supports JWT and similar tokens
Minimal configuration required
Intercepts requests automatically
Handles retry logic on 401 errors
Suitable for
Apps using JWT authentication
Projects with frequent API interactions
Developers seeking reduced auth boilerplate
Mobile and web applications with session management
Teams prioritizing clean, maintainable auth code
Considerations
Requires integration with existing Dio setup
Limited to token-based auth flows
May need custom logic for non-standard token formats
Depends on external network availability for refresh
Not suitable for stateless or tokenless APIs
Original README
Original README snapshot from the linked source repository. Visit the repository for the latest content.
Fresh 🍋
A collection of packages for automatic token refresh in Dart and Flutter. Fresh handles refreshing, caching, and attaching authentication tokens transparently so your API calls just work.
Why Fresh?
Token-based authentication seems simple until you handle the edge cases: tokens expire mid-session, multiple requests fail at the same time triggering duplicate refreshes, refresh tokens get revoked, and you need to route users to login when auth is lost. Fresh handles all of this so you don't have to.
No more manual 401 handling scattered across your codebase
No more race conditions when concurrent requests trigger simultaneous refreshes
No more stale tokens causing request failures - expired tokens are refreshed proactively before the request is even sent