Caching SdashAPI Responses

Caching saves you money by drastically reducing the number of requests you make to our servers (protecting your monthly quota). It also makes your application feel incredibly fast to the user, as cached questions can be loaded instantly from their device's memory without waiting for a network round-trip.

If you are building a web application, you can easily save fetched batches of questions into the browser's localStorage or sessionStorage.

// Before making an API call, check if we already have the data
const cachedData = localStorage.getItem('jamb_physics_2019');

if (cachedData) {
  // Use the instantly available local data
  renderQuiz(JSON.parse(cachedData));
} else {
  // Otherwise, fetch from SdashAPI
  fetch('https://sdashapi.com/api/v1/q?subject=physics&year=2019&limit=50', { headers })
    .then(res => res.json())
    .then(json => {
      // Save it to localStorage for next time!
      localStorage.setItem('jamb_physics_2019', JSON.stringify(json.data));
      renderQuiz(json.data);
    });
}

If you are proxying requests through your own Node.js or PHP backend, you should implement an in-memory cache like Redis. When User A requests WASSCE Mathematics questions, your backend fetches them from SdashAPI and saves them to Redis. When User B requests the exact same test 10 minutes later, your backend serves the questions instantly from Redis without consuming any SdashAPI credits.