Quickstart

Quickstart: send a message to the support chat endpoint

POST /public/v1/support/chat powers a conversational support experience. Post the visitor's message with a conversation id and read back the assistant's reply — enough to build a fully custom chat surface on top of Credicorp's public support brain.

2 min read

POST/public/v1/support/chat
conversation_idThreads context
replyAssistant answer

Send a message

curl -s -X POST https://api.credicorp.co.uk/public/v1/support/chat \
  -H 'Content-Type: application/json' \
  -d '{
    "conversation_id": "conv_8a1c",
    "message": "What is the maximum I can borrow for six months?"
  }'

The response carries the assistant reply and the conversation_id to reuse on the next turn. Keep sending the same id to preserve context across the conversation.

Wire it into your UI

async function ask(conversationId, message) {
  const res = await fetch(`${BASE}/support/chat`, {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({ conversation_id: conversationId, message }),
  });
  const { reply } = await res.json();
  return reply;
}

Frequently asked questions

How do I keep conversation context?

Reuse the same conversation_id across turns. Start a new conversation by omitting it on the first message and storing the id the response returns.

Is this the same as the MCP server?

No. This is a support chat surface for end users. The MCP server exposes tools to AI agents. They serve different audiences.

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.