Quickstart

Quickstart: use the Credicorp public API in AWS Lambda

Here is the idiomatic way to call the Credicorp public API from AWS Lambda. 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

AWS LambdaIdiomatic integration
cacheCatalogue changes rarely
configBase URL from env

Call the API from AWS Lambda

export const handler = async () => {
  const res = await fetch('https://api.credicorp.co.uk/public/v1/products');
  const body = await res.json();
  return {
    statusCode: 200,
    headers: { 'content-type': 'application/json', 'cache-control': 'max-age=3600' },
    body: JSON.stringify(body),
  };
};

In a Lambda (Node 18+ runtime) the global `fetch` calls the API with no bundled dependencies. Keep the base URL in an environment variable and any partner secret in AWS Secrets Manager or an encrypted env var, read at cold start.

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

How do I keep secrets in Lambda?

Use AWS Secrets Manager or KMS-encrypted environment variables and read them at cold start. Never bake a partner secret into the deployment package.

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.