Quickstart: Proxy the public API through your

Q: Does proxying change caching?

You control the cache at the proxy. Respect the upstream Cache-Control as a floor and add your own longer TTL if it suits your traffic.

2 min read

one originFront-end talks to you

cacheAdd your own TTL

shapeTrim to what you need

A minimal proxy

app.get('/api/products', async (req, res) => {
  const upstream = await fetch(`${process.env.CREDICORP_BASE}/products`);
  const { data } = await upstream.json();
  const slim = data.map(({ id, name, min_amount, max_amount }) =>
    ({ id, name, min_amount, max_amount }));
  res.set('Cache-Control', 'public, max-age=3600').json(slim);
});

Why proxy at all

Proxying gives you caching, payload shaping and a single origin for your SPA. Crucially, it is the natural home for authenticated partner calls later — the secret lives on the server and never reaches the browser.

Frequently asked questions

Is proxying necessary?

No for pure public reads, but it pays for itself once you want caching, payload shaping, or to add authenticated partner calls without exposing secrets.

Does proxying change caching?

You control the cache at the proxy. Respect the upstream Cache-Control as a floor and add your own longer TTL if it suits your traffic.