Skip to main content
Credit Benchmark
Credit BenchmarkApril 29, 2026 · 2 min read
The Matching API is a new endpoint for resolving external company names to Credit Benchmark reference entities — so you can standardize identifiers before portfolios load, before analytics run, before anything downstream depends on the data being clean.
Endpoint: POST /matching/text/match_externalReturns ranked candidates with CBId, CBEntityName, CBCountryOfRiskISO, and a confidence score. Pass optional hints — country, industry, lei — to sharpen results when names are ambiguous.

​
The problem

Company names are messy. “JPMorgan”, “JP Morgan Chase & Co.”, and “JPMorgan Chase” are the same entity — but not to a system that needs exact identifiers. Before this API, resolving that ambiguity meant manual work or custom matching logic built outside CB entirely.

​
What it does

Send a name, get back a ranked list of entity candidates. Each result includes:
  • CBId — the canonical CB identifier
  • CBEntityName — the standardized entity name
  • CBCountryOfRiskISO — country of risk
  • confidence — a score you can use to automate decisions: accept high matches, flag low ones for review

​
Use cases

  • Portfolio onboarding — map client-supplied names to CB identifiers before loading, so data enters clean rather than requiring cleanup after
  • Automated workflows — any pipeline ingesting external entity lists can run a matching pass upfront and carry reliable identifiers forward
  • One-off lookups — resolve a single name before pulling analytics or checking coverage, without leaving the API

​
Getting started

  1. Get a bearer token — POST /api/security/token
  2. Submit names — POST /matching/text/match_external
  3. Read the schema — API reference
← All release notes