General Usage Limits and Values for the Sensedia API Platform

Usage limits are essential to ensure the stability, performance, and security of the Sensedia API 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.

Analytics

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.

Sensedia API Platform resource limits

Maximum routes created: 10,000 per Gateway Pool.
See also:

What are routes?

How do I know the current number of set up routes?
Default timeout: The gateway operates with a default timeout of 60 seconds.

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.

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.

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. Rationalization actions and best practices may be recommended.
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. Adjustments may be required to maintain support for performance and scalability.

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.
Rationalization actions and best practices may be recommended.

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.
Adjustments may be required to maintain support for performance and scalability.

General values for the Sensedia API Platform

Access
- Session timeout: 15 minutes
- Password expiration: 90 days

Thanks for your feedback!

EDIT

Share your suggestions with us!
Click here and then [+ Submit idea]