Quickstart: call the Creditcorp public API from

Q: Should I new up HttpClient per request?

No — that exhausts sockets. Use one shared instance or IHttpClientFactory, which manages the lifetime and connection pool for you.

Q: How do I handle errors in C# / .NET?

Check the status code and read the error object from the body — error.code is the stable machine string to branch on. The pattern is identical across every endpoint.

2 min read

C# / .NETFirst call

timeoutBound every request

data[]Unwrap the envelope

List products

using var http = new HttpClient { Timeout = TimeSpan.FromSeconds(10) };
http.DefaultRequestHeaders.Accept.Add(new("application/json"));
var res = await http.GetAsync("https://api.credicorp.co.uk/public/v1/products");
res.EnsureSuccessStatusCode();
var json = await res.Content.ReadFromJsonAsync<ProductList>();

Use a single shared HttpClient (never one per call) and ReadFromJsonAsync with a typed record. Register it via IHttpClientFactory in ASP.NET Core for pooling and resilience policies.

Use the sandbox in development

Point the base host at https://sandbox.credicorp.co.uk/public/v1 in development and CI, and at https://api.credicorp.co.uk/public/v1 in production, driven by one environment variable. See choosing a base URL.

Next steps

From here, request a quote, submit an enquiry, and send applicants to apply. Handle errors with the shared error envelope.

Frequently asked questions

Should I new up HttpClient per request?

No — that exhausts sockets. Use one shared instance or IHttpClientFactory, which manages the lifetime and connection pool for you.

How do I handle errors in C# / .NET?

Check the status code and read the error object from the body — error.code is the stable machine string to branch on. The pattern is identical across every endpoint.