Quickstart

Quickstart: use the Credicorp public API in Next.js

Here is the idiomatic way to call the Credicorp public API from Next.js. Fetch the product catalogue, cache it, and read the base host from configuration — the same shape you extend later for pricing and quotes, always keeping partner secrets server-side.

2 min read

Next.jsIdiomatic integration
cacheCatalogue changes rarely
configBase URL from env

Call the API from Next.js

// app/products/page.tsx (Server Component)
export default async function Products() {
  const res = await fetch('https://api.credicorp.co.uk/public/v1/products', {
    next: { revalidate: 3600 },  // cache for an hour
  });
  const { data } = await res.json();
  return <ProductGrid products={data} />;
}

Fetch in a Server Component so the call happens on your server, out of the browser, and use `next.revalidate` to cache the catalogue. This is also the right place to add partner-ring calls later, since server components keep secrets server-side.

Point at sandbox in development

Set the base URL to https://sandbox.credicorp.co.uk/public/v1 in development and CI, and to https://api.credicorp.co.uk/public/v1 in production — driven by the one environment variable your framework already exposes. See choosing a base URL.

Next steps

From here you can add a quote form, an enquiry submission or an embeddable product picker. Send applicants to apply to start a real journey.

Frequently asked questions

Server or client component?

Fetch public data in a Server Component and cache it with revalidate. Only drop to a Client Component for interactivity, and never call an authenticated endpoint from one.

Should I cache the product list?

Yes. The catalogue changes infrequently, so cache it for the response's max-age. This keeps the API off your hot path and well under the rate limit.

Funding for UK limited companies

Credicorp lends to your company, not to you personally — short-term working capital with no personal guarantee. See what your business could access.