Start using cache

Table of Contents

Use Cases

What is SkipRequest?

Simplify API Management with SkipRequest

SkipRequest transforms the way you handle API requests. With just a simple change in your API endpoint's domain to include yourClientId.skiprequest.com, you unlock powerful caching capabilities. This means if an identical request has been made before, you instantly get the cached response, reducing load on your servers and cutting down costs. No need for complex configurations, just a straightforward domain change.

Authentication

Seamless Authentication with SkipRequest to other APIs

SkipRequest acts as a transparent pass-through proxy, meticulously preserving the integrity of your API calls. Our system ensures your existing authentication process remains untouched, forwarding your headers and requests as is to the end provider whenever a cache miss occurs.

Authenticating with SkipRequest

To authenticate with SkipRequest, you'll be assigned a unique domain such as YOUR_ID.skiprequest.com. This domain is key to managing your requests and ensuring that your API calls are recognized and verified within our system.

Here's how we handle your API keys securely:

  • On each request we check the AUTHENTICATION header for a key. This could be an API_KEY, BEARER_TOKEN, etc
  • We do not store your full keys. Instead, we hash each key using SHA256, appending the last three characters of the key for your easy identification in the admin dashboard.
  • The last three characters are solely for your reference to connect the hash with your key visually.

For enhanced security, especially for enterprise clients:

  • The above allows for simple integration where all you need to change is the api endpoint and not mess with headers. It has the drawback of having to approve every KEY in our dashboard
  • You can use your own API key by setting the header _skip_request_key
  • This header can carry a custom value that you create and approve in our dashboard, offering an extra layer of security. To be clear we do NOT create this value, it is internal to you. When set we skip checking the authentication header and use this value instead
  • This is very useful if you will be changing your API keys with the end service as you will not need to make any changes inside SkipRequest. It is also useful for Enterprise grade security where you want to minimize where your keys are stored even though we are hashing and only using the last 3 characters

Integration

Most Common Use Case: requests

Many APIs are called directly and the following code shows you how to do that really easily in multiple languages. Consider the following example where we want to know what language something is in. Our phrase is "Είναι όλα ελληνικά για μένα". We will use Google's translate API https://translation.googleapis.com/language/translate/v2/detect which will translate to: https://translation-googleapis-com-{YOUR_ID}.skiprequest.com/language/translate/v2/detect

const axios = require("axios");
let data = JSON.stringify({q: "Είναι όλα ελληνικά για μένα"});
let config = {
  method: "post",
  maxBodyLength: Infinity,
  url: "https://translation-googleapis-com-{YOUR_ID}.skiprequest.com/language/translate/v2/detect",
  headers: {
    "X-goog-api-key": "{YOUR_GOOGLE_API_KEY}",
    "Content-Type": "application/json",
  },
  data: data,
};

axios
  .request(config)
  .then((response) => {
    console.log(JSON.stringify(response.data));
  })
  .catch((error) => {
    console.log(error);
  });
The RESPONSE will be
{
  "data": {
    "detections": [[{
      "language": "el",
      "isReliable": false,
      "confidence": 1
    }]]
  }
}

Use Cases

The following list are some useful APIs that are effective at being cached