Lloyd's of London

Lloyd's Catastrophe Codes API v1

Lloyd's catastrophe event reference data served from the London Market API Gateway — the market's canonical codes for aggregating losses to a named catastrophe (e.g. 17E "Typhoon Hato, 20 August 2017 and ongoing, affecting Hong Kong, Macau and South China"), each carrying Code, Definition, EventStartDate, EventEndDate and EventYear. This API was never listed in the Lloyd's API catalogue; it surfaced because the Lloyd's Base API Standard uses it for every worked example of the identity pseudo-field and the collection wrapper document. It is the only Lloyd's API surface still routed on the gateway: probed on 2026-07-25 the unauthenticated /health meta resource mandated by section 5.11 of the Base API Standard returns 200 on both Production and Sandbox, while /CatastropheCodes and /version return 401 {"Code":401,"Message":"Client certificate is missing."} — the mutual-TLS gate is live and enforcing. Access requires LIMOSS Common Services onboarding, an Azure AD on-behalf-of token with scp=user_impersonation, and a registered X.509 certificate per environment. No specification is published.

GitHub

Documentation

📖
Documentation
https://web.archive.org/web/20200930095802/https://developer.lloyds.com/Get-Started/Base-API-Standard
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/lloyds-of-london/refs/heads/main/authentication/lloyds-of-london-authentication.yml

Other Resources

🔗
Examples
https://raw.githubusercontent.com/api-evangelist/lloyds-of-london/refs/heads/main/examples/_index.yml
🔗
Sandbox
https://raw.githubusercontent.com/api-evangelist/lloyds-of-london/refs/heads/main/sandbox/lloyds-of-london-sandbox.yml
🔗
WellKnown
https://api.londonmarketgroup.co.uk/discovery/.well-known/openid-configuration

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/lloyds-catastrophe-codes-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: lloyds-of-london:lloyds-catastrophe-codes-api
name: Lloyd's Catastrophe Codes API v1
description: 'Lloyd''s catastrophe event reference data served from the London Market API Gateway — the
  market''s canonical codes for aggregating losses to a named catastrophe (e.g. 17E "Typhoon Hato, 20
  August 2017 and ongoing, affecting Hong Kong, Macau and South China"), each carrying Code, Definition,
  EventStartDate, EventEndDate and EventYear. This API was never listed in the Lloyd''s API catalogue;
  it surfaced because the Lloyd''s Base API Standard uses it for every worked example of the identity
  pseudo-field and the collection wrapper document. It is the only Lloyd''s API surface still routed on
  the gateway: probed on 2026-07-25 the unauthenticated /health meta resource mandated by section 5.11
  of the Base API Standard returns 200 on both Production and Sandbox, while /CatastropheCodes and /version
  return 401 {"Code":401,"Message":"Client certificate is missing."} — the mutual-TLS gate is live and
  enforcing. Access requires LIMOSS Common Services onboarding, an Azure AD on-behalf-of token with scp=user_impersonation,
  and a registered X.509 certificate per environment. No specification is published.'
humanURL: https://web.archive.org/web/20200930095802/https://developer.lloyds.com/Get-Started/Base-API-Standard
baseURL: https://api.londonmarketgroup.co.uk/Lloyds/CatastropheCodes/v1
tags:
- Catastrophe
- Reference Data
- London Market
- Reinsurance
properties:
- type: Documentation
  url: https://web.archive.org/web/20200930095802/https://developer.lloyds.com/Get-Started/Base-API-Standard
  name: Lloyd's Base API Standard
  description: The normative standard this endpoint implements, and the source of its published payload
    examples.
- type: Examples
  url: examples/_index.yml
- type: Sandbox
  url: sandbox/lloyds-of-london-sandbox.yml
  name: Sandbox environment
  description: https://sand-api.londonmarketgroup.co.uk/Lloyds/CatastropheCodes/v1 — live, /health returns
    200; access is partner-gated via LIMOSS.
- type: Authentication
  url: authentication/lloyds-of-london-authentication.yml
- type: WellKnown
  url: https://api.londonmarketgroup.co.uk/discovery/.well-known/openid-configuration
  name: OpenID Connect discovery
  description: Live OIDC discovery document mandated by section 5.12.2 of the Lloyd's Base API Standard;
    references the gateway JWKS at /discovery/keys.