Fair usage policy
Powens implements a Fair Usage Policy to ensure optimal API performance for all users.
Last updated
Was this helpful?
Powens implements a Fair Usage Policy to ensure optimal API performance for all users.
Last updated
Was this helpful?
The Fair Usage Policy (FUP) is designed to ensure a smooth, reliable, and efficient experience for all users of the Powens API. By setting reasonable usage limits, we help maintain optimal performance, security, and stability, while preventing unintentional system overload.
Rather than being a restriction, this policy guarantees fair access for all users and ensures that our API remains high-performing and scalable as open finance evolves.
As open finance expands and new use cases emerge, API traffic has naturally increased due to larger data volumes and more frequent updates. Anticipating this, we designed robust solutions such as and Background Refresh to handle data synchronization efficiently.
To keep our API fast and available for everyone, we strongly recommend using first rather than repeatedly polling the API. Webhooks allow us to push real-time updates directly to you, ensuring a smoother and more efficient integration.
When Webhooks are not an option, excessive requests in a short timeframe can put unnecessary strain on the system, potentially affecting performance for all users. To prevent this, we have introduced rate limiting, ensuring fair resource allocation and protecting both sandbox and production environments.
There are legitimate scenarios where a manual refresh is required, for example:
When an end user actively requests a data update (e.g., opening the app or starting a credit application).
When the refresh is for a single user, not a bulk operation on multiple users.
Our Webhooks system is robust, reliable, and designed for scalability—helping you optimize your integration while keeping the Powens API stable for all users.
Before diving into rate limits, let’s clarify the role of our Sandbox environment:
Developing and testing your integration.
Load testing or simulating high API traffic.
Validating new features before going live.
Production-like scenarios (it does not contain real user data).
Since the Sandbox is meant for functional testing, rate limits ensure that it remains available and efficient for all developers.
Default
30 call/min
86400
To maintain high performance and reliability, we strongly encourage you to adopt whenever possible. They eliminate unnecessary API polling, improve efficiency, and ensure seamless real-time updates.