Quickstart

Quickstart: fetch published CMS content by key

GET /public/v1/cms/pages/{key} serves published Credicorp content by a stable key. Use it to pull canonical copy — a legal notice, a product blurb, a disclosure — into your own page so it stays in sync with the source of truth instead of being copied and left to rot.

2 min read

GET/public/v1/cms/pages/{key}

keyStable content id

canonicalSingle source of truth

Fetch a page by key

curl -s https://api.credicorp.co.uk/public/v1/cms/pages/representative-example \
  -H 'Accept: application/json'

The response carries the content title, the body (as sanitised HTML or Markdown) and a updated_at timestamp. Cache it and refresh when updated_at changes so your copy is never stale.

Why pull instead of copy

Regulated copy — a representative example, a risk warning — must match the source exactly. Fetching it by key means a change on our side propagates to your integration automatically, with no manual re-paste and no drift.

Frequently asked questions

What keys are available?

Keys are documented per content item in the reference. Treat them as stable identifiers; an unknown key returns a 404.

Is the body safe to render?

The body is sanitised server-side, but always render it through your own sanitiser as defence in depth, especially if you inject it into a page with other scripts.