Rate Limits & Best Practices

Rate Limits and Best Practices

The JKT48Connect system enforces Rate Limiting protection to maintain server performance, ensure response time stability, and provide an equitable experience for all users.

Basic Concepts of API Keys & Throttling

Each API key has a maximum request quota that cannot be exceeded in rapid succession. The system automatically detects aggressive querying and will return an HTTP response status of 429 Too Many Requests if you exceed your daily access limit or spam queries consecutively per second.

Exceeding the Limit Indicator:

{
  "status": false,
  "message": "You have exceeded your daily API limit or sending too many requests."
}

HTTP Code: 429

If you encounter this code, your integration function must temporarily sleep/delay its execution. Never force queries inside an unnatural loop (while (true) without a break delay), as this runs the risk of account deactivation and IP Address blacklisting.

Integration Best Practices

Implement standard, optimized network call procedures to minimize excessive hits against the JKT48Connect backend servers:

1. Implement Application-Level Caching (Server-side)

Instead of designing functions that call the JKT48Connect API directly every time there is a user interaction, temporarily store the API results in local memory (memcached, redis, or simply a standard memory variable within your framework like PHP/Node.JS) before rendering them en masse.

Simple JS memory caching scheme example:

let cacheMembers = null;
let lastFetchTime = 0;
const CACHE_TTL_MS = 60 * 60 * 1000; // 1 Hour. (Highly recommended to limit traffic)

async function getMembersList() {
    const now = Date.now();
    // Cache is still fresh
    if (cacheMembers !== null && (now - lastFetchTime) < CACHE_TTL_MS) {
        return cacheMembers; 
    }
    
    // Pull fresh data from the API network
    const res = await fetch(`https://v2.jkt48connect.com/api/jkt48/members?apikey=${KEY}`);
    const data = await res.json();
    
    // Update Cache State
    cacheMembers = data;
    lastFetchTime = now;
    
    return data;
}

2. Fetch Specific Resources Only When Needed

Most sections of your website do not require a fresh live feed on every page load. Only make a GET request to api/jkt48/live if the end-user is actively visiting the relevant screen/activity in your mobile app, not passively running it continuously in the background unless specifically designed with a per-minute sleep cooldown.

3. Keep Your API Key Secret (No Exposure)

While JKT48Connect does not block you from executing a Frontend Fetch Request via the Browser, doing so exposes your secret query parameter ?apikey=. This allows users to intercept, hijack, or mass-utilize your key on spam bots.

Build your own internal Backend Proxy Server if you intend to create a static website (like React / Vue), directing frontend requests to your proxy first, where your real API keys are securely filtered and appended.