Quickstart: use the Credicorp public API in

2 min read

SvelteKitIdiomatic integration

cacheCatalogue changes rarely

configBase URL from env

Call the API from SvelteKit

// +page.server.js
export async function load({ fetch }) {
  const res = await fetch(
    'https://api.credicorp.co.uk/public/v1/products');
  const { data } = await res.json();
  return { products: data };
}

Fetch in a SvelteKit load function on the server so the call stays out of the browser, and cache with setHeaders. The returned data is available to your +page.svelte.

Sandbox first

Set the base URL to https://sandbox.credicorp.co.uk/public/v1 in development and CI. See choosing a base URL.

Next steps

Add a quote form or an enquiry submission, and send applicants to apply. Handle failures with the shared error envelope.

Frequently asked questions

Should I cache the catalogue in SvelteKit?

Yes — it changes infrequently. Cache it for the response's max-age using SvelteKit's caching layer, so the API stays off your hot path and under the rate limit.

Where does the base URL belong?

In SvelteKit's configuration, read from an environment variable per environment, so the same build runs against sandbox and production by changing one value.