Thanks for your feedback!
EDIT
General Usage Limits and Values for the Sensedia Platform
Usage limits are essential to ensure the stability, performance, and security of Sensedia Platform. They help optimize resources, preventing overloads that could impact performance. On this page, you will find usage limits, default values, and best practices for using the platform efficiently. For custom adjustments, please contact our Support team.
Data retention limits
-
API Timeline: 60 days (in PCI-DSS certified environments, this period may vary*).
-
Audit Logs: 30 days (in certified environments, this period may vary*).
-
Stored Data: 7 days and up to 100 GB (additional storage can be purchased*).
*Consult CS/Support/Sales
API Management resource limits
-
Maximum routes created: 10,000 per Gateway Pool.
-
Default timeout: The gateway operates with a default timeout of 60 seconds.
Log limits
-
Maximum log size per request: 1 MB in the Trace section.
When this limit is exceeded, the log interceptor stops recording the transmitted content and the log entry displays a warning message instead.
The limit applies only to the log entry and does not interrupt the processing of the request by the gateway. For the size of the request itself, see Runtime Payload.
To preserve the log entry in requests that exceed the limit, use the Log Obfuscation interceptor, which allows you to omit certain payload information to optimize the log entry.
Recommended Operational Limits
Access Token and Refresh Token
The table below summarizes the recommended limits related to OAuth 2.0 authentication.
| Limit name | Value | Status | Notes / Impact |
|---|---|---|---|
Access Token— expiration time (OAuth 2.0) |
Minimum: 5 minutes Maximum: 24 hours |
Recommended* |
Higher values increase security risks, make revocation more difficult, and may lead to unpredictable behavior. |
Refresh Token— expiration time |
Minimum: 5 minutes Maximum: 90 days |
Recommended* |
The Refresh Token must not expire before the Access Token it renews. Very long expirations increase security risks and operational impact on the gateway. |
|
* The limits listed in this section are recommended and subject to future enforcement. |
Runtime Payload
The table below defines the recommended limits for request and response sizes processed by the gateway during API execution(runtime).
| Limit name | Value | Status | Notes / Impact |
|---|---|---|---|
Runtime payload — maximum size per request/response |
32 MB |
Recommended* |
Larger payloads increase memory consumption, latency, and impact on interceptors, logs, and metrics. The platform is not intended for transferring files or blobs. |
|
* The limits listed in this section are recommended and subject to future enforcement. |
Environment Variables
The following table presents the recommended operational ranges for the use of environment variables per environment.
These limits were defined to preserve platform performance, reduce resource consumption, and maintain operational predictability in high-volume environments.
| Usage range | Number of variables | Status | Notes / Impact |
|---|---|---|---|
Normal |
Up to 100 |
Supported |
Operates within the platform’s expected envelope, with performance and stability aligned with product SLOs. |
High complexity |
From 101 to 200 |
Supported with potential performance impact |
May experience performance degradation in complex environments. |
Critical risk |
Above 200 |
Outside the recommended operational envelope |
Operates outside the recommended envelope, with risk of unpredictable behavior, increased latency, excessive resource consumption, and stability impacts. |
Number of Apps
Controlling the number of registered apps is essential to ensure the stability, performance, and predictability of the Sensedia Platform. Each app represents an active credential that the platform must maintain, synchronize, and take into account when routing requests.
The following table presents the recommended operational ranges for the number of registered apps.
| Usage range | Number of apps | Status | Notes / Impact |
|---|---|---|---|
Normal |
Up to 80,000 |
Supported |
Operates within the platform’s expected envelope, with performance and stability aligned with product SLOs. |
High complexity |
From 80,001 to 100,000 |
Supported with potential performance impact |
May experience performance degradation in environments with a large volume of apps. |
Critical risk |
Above 100,000 |
Not supported |
Above 100,000 apps, the platform does not guarantee correct operation and may present unexpected errors, unpredictable behavior, increased latency, excessive resource consumption, and stability impacts. |
General values for the Sensedia Platform
-
Access
-
Session timeout: 15 minutes
-
Share your suggestions with us!
Click here and then [+ Submit idea]