Overview

This article explains the response policy for the Kamino API. Partners often ask if they can cache API responses to improve local performance. Caching API responses isn't authorized.

Response time

Many new partners request caching because they assume response speed might be an issue. However, the current average response time is 50 ms, and the infrastructure maintains 99.9% uptime.

Most clients drop the caching request once they observe the real-time performance of the API and the reliability of the infrastructure.

Why caching is not permitted

Data reconciliation impact

Reporting and billing systems depend on real-time, uncached data to ensure accuracy across the following areas:

• Budget pacing:  Caching causes inconsistencies that compromise data reconciliation between systems.
• Data consistency: The system links each tracked event, such as an impression, click, or view, to an ad request ID. Pre-ingestion and post-ingestion systems use this ID for data consistency checks. Ad events expire 20 minutes after the source ad request triggers.
• Report consistency: Specific reports, for example, the Fill Rate report, rely heavily on real-time ad requests.

Budget pacing and delivery logic

Ad delivery and pacing algorithms rely on live API responses to perform the following tasks:

• Enable advanced targeting features, such as frequency capping, user segmentation, and non-exposure logic.
• Ensure campaign spend stays within budget caps.
• Support real-time bidding from advertiser campaigns.

Introducing caching layers can disrupt these mechanisms and lead to overdelivery or underdelivery, resulting in financial and operational impacts for both parties.

Technical complexity and maintenance risk

Supporting caching requires a significant architectural overhaul, custom invalidation strategies, and high maintenance burdens across integrations. Equativ classifies this development internally as an XXL-level effort.

Best practices

To avoid delivery limitations and architectural complexity, follow these initial steps:

Assess real-time API performance

Test API response times under realistic conditions. If you need to prevent performance impacts on your application, implement timeouts or fallbacks.

Define targeted caching scenarios

Identify which parts of your website or application benefit from short-term or session-level data reuse. For example, you can cache static or non-sensitive elements like product information or ad creative assets to improve client-side rendering performance. Do not include tracking beacons in your cache.

These lightweight strategies enhance perceived speed without creating risks to real-time logic or data integrity.

Collaborate closely with our teams

Our team is available to iterate with you. We help you explore solutions that meet your technical goals while preserving the accuracy and integrity of the data pipeline.

Although persistent caching is not permitted, Equativ helps you find scalable, high-performance alternatives that align with your product and business needs. These steps ensure that we identify the right features and architecture for your use case.