Package selection guidance compiled from public package information, community data, and project usage.
Fresh Http is a Flutter/Dart package that provides an auto-refreshing HTTP client built on top of the `http` package. It automatically handles authentication token refreshes, ensuring seamless API calls without manual token management. Ideal for apps requiring secure, persistent access to authenticated APIs, it reduces boilerplate and improves reliability by transparently refreshing expired tokens. The client integrates smoothly with existing HTTP workflows and supports all major platforms including web, mobile, and desktop.
Use cases
APIs requiring token refresh
Secure mobile and web applications
Reducing authentication boilerplate
Automated token management
Stateful API clients
Key features
Automatic token refresh
Built on `package:http`
Transparent auth handling
Cross-platform support
Minimal setup required
Suitable for
Apps with JWT or OAuth2
Developers seeking reduced auth complexity
Projects needing reliable API connectivity
Teams prioritizing developer experience
Applications with frequent API interactions
Considerations
Requires custom token refresh logic
Depends on external auth state management
Limited to HTTP-based APIs
Not suitable for one-off requests
Needs proper error handling in token refresh flow
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