Testing Your SuperAPI Gateway

Quick Cache Test

Now that you've configured your endpoints and deployed your gateway, let's verify that caching is working correctly with a simple test.

Making Your First Cached Request

Use this example to test your SuperAPI gateway:

curl -I -X GET \
  -H "Authorization: Bearer $YOUR_JWT_TOKEN" \
  -H 'Content-Type: application/json' \
  -H 'SS4-HOST: api.your-origin-server.com' \
  'https://your-gateway.superapi.cloud/your/endpoint/path'

Replace:

$YOUR_JWT_TOKEN with your actual JWT token (if authentication is configured)
api.your-origin-server.com with your origin server hostname
your-gateway.superapi.cloud with your SuperAPI DNS endpoint
/your/endpoint/path with one of your configured cached endpoints

What to Look For

In the response headers, you should see:

First request:

ss4-cache: MISS - Response fetched from your origin server and cached

Second identical request:

ss4-cache: HIT - Response served directly from SuperAPI's cache

A cache HIT means SuperAPI successfully cached your API response and is now serving it without contacting your origin server, dramatically improving response times.

Verifying Performance Improvement

Add timing to see the speed difference:

# Add timing to measure performance
curl -w "\nTotal time: %{time_total}s\n" -X GET \
  -H "Authorization: Bearer $YOUR_JWT_TOKEN" \
  -H 'SS4-HOST: api.your-origin-server.com' \
  'https://your-gateway.superapi.cloud/your/endpoint/path'

Cache HITs should be significantly faster than cache MISSes.

🧪

Comprehensive Testing Guide

For detailed testing scenarios, cache invalidation testing, and troubleshooting, see our complete testing guide.

Now that you've successfully deployed your SuperAPI gateway and verified that caching is working with your test requests, you can monitor your API's performance improvements through the comprehensive metrics dashboard.

View Performance Metrics

Monitor cache hit rates, request latencies, and invalidation patterns in real-time.