Lloyd's of London

aid: lloyds-of-london
url: https://raw.githubusercontent.com/api-evangelist/lloyds-of-london/refs/heads/main/apis.yml
name: Lloyd's of London
kind: company
description: 'Lloyd''s of London is the world''s specialist insurance and reinsurance market, operating as a regulated marketplace
  rather than as a carrier: the Corporation of Lloyd''s oversees syndicates, managing agents, brokers and coverholders who
  underwrite property, casualty, marine, aviation, energy, cyber, political risk and reinsurance business on a subscription
  basis from its home market in the United Kingdom. Its API posture reflects that role. Lloyd''s is a standards and market-infrastructure
  publisher first — the Core Data Record (CDR), the Market Reform Contract (MRC), coverholder and delegated claims reporting
  standards, and Blueprint Two digital processing requirements — and its technical surface is aimed at brokers, syndicates
  and market vendors, not at outside developers. Lloyd''s ran a public API Development Portal at developer.lloyds.com (the
  "API Factory", BETA from June 2020) that published a Base API Standard and a catalogue of three market APIs: Placing — Submission
  and Quote, Placing — Firm Order, and RPAC for delegated authority risk, premium and claims. That portal now redirects to
  www.lloyds.com and no replacement self-serve developer portal is published. Production access to the underlying London Market
  API gateway (https://api.londonmarketgroup.co.uk) has always been partner-gated: an organisation must be onboarded to LIMOSS
  Common Services, registered in the Common Services Azure Active Directory tenant, and register an X.509 certificate before
  it can call anything. There is no public, self-serve Lloyd''s API, no public sandbox and no public downloadable specification
  reachable today — the honest record for this market body is documentation-and-standards-first. What Lloyd''s does still
  operate, verified by live probe, is a genuine gated API estate: three isolated gateway environments (Sandbox, PreProd, Production),
  an OpenID Connect discovery document and JWKS published on each, and a routed Catastrophe Codes v1 endpoint whose unauthenticated
  /health meta resource answers 200 while its data resources return 401 "Client certificate is missing". Its most reusable
  public artifact is the Lloyd''s Base API Standard — a normative RFC 2119 document fixing the resource model, query grammar,
  collection and error envelopes, versioning compatibility rules and the dual mutual-TLS + JWT security model for every API
  published to the market.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Insurance
- United Kingdom
- Reinsurance
- Specialty Insurance
- London Market
- Underwriting
- Claims
- Delegated Authority
- Broker
- Market Infrastructure
- Standards
- ACORD
created: '2026-07-25'
modified: '2026-07-25'
specificationVersion: '0.19'
apis:
- aid: lloyds-of-london:lloyds-placing-api-submission-and-quote
  name: Lloyd's Placing API - Submission and Quote v1
  description: Market API for electronic placement in the London subscription market — create submissions and submission versions,
    upload Market Reform Contract and quote documents, add carriers and underwriters to a submission, send requests for quote,
    and receive underwriter responses (reject, express interest, request for information, or quote). Published by Lloyd's
    under the API Factory programme with a Swagger/OpenAPI 3.0 document (Swagger_PlacingSubmissionAndQuote_v1.10.202004160916.json)
    offered for download from the developer portal. Access is partner-gated to onboarded London Market organisations via LIMOSS
    Common Services, Azure AD tokens and a registered X.509 certificate; the developer portal that hosted the reference and
    the specification now redirects to www.lloyds.com, so the spec could not be harvested. Covers the QUOTE verb of the insurance
    lifecycle, broker-to-carrier only.
  humanURL: https://developer.lloyds.com/placingsubmissionandquote-v1/Developer-Overview
  baseURL: https://api.londonmarketgroup.co.uk/PPL/Lloyds/Placing/V1
  tags:
  - Placement
  - Submission
  - Quote
  - London Market
  properties:
  - type: Documentation
    url: https://web.archive.org/web/20210128061829/https://developer.lloyds.com/placingsubmissionandquote-v1/Key-Details-On-API
  - type: APIReference
    url: https://web.archive.org/web/20210128055606/https://developer.lloyds.com/placingsubmissionandquote-v1/Technical-Model
  - type: Documentation
    url: https://web.archive.org/web/20200930095802/https://developer.lloyds.com/Get-Started/Base-API-Standard
  - type: Authentication
    url: https://web.archive.org/web/20200930085423/https://developer.lloyds.com/Get-Started/Authentication-Information
- aid: lloyds-of-london:lloyds-placing-api-firm-order
  name: Lloyd's Placing API - Firm Order
  description: Second Placing API listed in the Lloyd's API catalogue, described by Lloyd's as "Finalise Placings, Bind Risks,
    Sign Transactions" — the BIND verb of the insurance lifecycle for the London subscription market. Only a catalogue-level
    description was ever published publicly; no reference documentation, base URL or downloadable specification is reachable,
    and the developer portal that carried the catalogue now redirects to www.lloyds.com. Partner-gated to onboarded market
    participants.
  humanURL: https://web.archive.org/web/20200610082013/https://developer.lloyds.com/Explore-Innovate
  tags:
  - Placement
  - Firm Order
  - Bind
  - London Market
  properties:
  - type: Documentation
    url: https://web.archive.org/web/20200610082013/https://developer.lloyds.com/Explore-Innovate
- aid: lloyds-of-london:lloyds-rpac-api
  name: Lloyd's RPAC API (Risk, Premium and Claims)
  description: Third API listed in the Lloyd's API catalogue, described by Lloyd's as "Submit Risk, Premium and Claims details
    for Delegated Authority Placements" — the delegated authority reporting path that carries risk, premium and claims (FNOL-adjacent)
    data from coverholders and delegated claims administrators into the market, aligned to Lloyd's Coverholder Reporting Standards
    and ACORD technical standards. Only a catalogue-level description was ever published publicly; no reference documentation,
    base URL or downloadable specification is reachable. Partner-gated to onboarded market participants.
  humanURL: https://web.archive.org/web/20200610082013/https://developer.lloyds.com/Explore-Innovate
  tags:
  - Delegated Authority
  - Risk
  - Premium
  - Claims
  properties:
  - type: Documentation
    url: https://web.archive.org/web/20200610082013/https://developer.lloyds.com/Explore-Innovate
  - type: Documentation
    url: https://www.lloyds.com/market-resources/delegated-authorities/market-knowledge/reporting-standards
- 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.
common:
- type: VulnerabilityDisclosure
  url: security/lloyds-of-london-vulnerability-disclosure.yml
- type: Security
  url: https://www.lloyds.com/security-reports
  name: Responsible Disclosure Programme
  description: Lloyd's responsible disclosure programme and researcher hall of fame; reports go to securityreporting@lloyds.com
    per the published RFC 9116 security.txt.
- type: SecurityTxt
  url: well-known/lloyds-of-london-security.txt
- type: DomainSecurity
  url: security/lloyds-of-london-domain-security.yml
- type: WellKnown
  url: well-known/lloyds-of-london-well-known.yml
  name: Well-known discovery surface
  description: Harvested /.well-known/ documents across the Lloyd's web estate and all three London Market API Gateway environments
    — security.txt plus live OIDC discovery and JWKS.
- type: Authentication
  url: authentication/lloyds-of-london-authentication.yml
- type: OAuthScopes
  url: scopes/lloyds-of-london-scopes.yml
- type: Conventions
  url: conventions/lloyds-of-london-conventions.yml
  name: Lloyd's Base API Standard as structured conventions
  description: Resource model, paging/ordering/filtering/selection/expansion grammar, collection and error envelopes, concurrency,
    versioning and meta resources.
- type: ErrorCatalog
  url: errors/lloyds-of-london-error-codes.yml
  name: Placing API error-code registry
  description: 107 named error codes plus the Base API Standard's HTTP status mapping rules.
- type: Examples
  url: examples/_index.yml
  name: Published request/response examples
  description: 22 payload examples captured verbatim from Lloyd's own documentation.
- type: DataModel
  url: data-model/lloyds-of-london-data-model.yml
- type: Lifecycle
  url: lifecycle/lloyds-of-london-lifecycle.yml
- type: ChangeLog
  url: changelog/lloyds-of-london-changelog.yml
- type: Conformance
  url: conformance/lloyds-of-london-conformance.yml
- type: Sandbox
  url: sandbox/lloyds-of-london-sandbox.yml
- type: LLMsTxt
  url: llms/lloyds-of-london-llms.txt
- type: Website
  url: https://www.lloyds.com/
- type: Support
  url: https://www.lloyds.com/contact-us
  name: Contact Lloyd's
- type: Blog
  url: https://www.lloyds.com/news-and-insights
  name: News and Insights
- type: TermsOfService
  url: https://www.lloyds.com/help/terms-and-conditions
- type: PrivacyPolicy
  url: https://www.lloyds.com/help/privacy
- type: Documentation
  url: https://www.lloyds.com/market-resources/requirements-and-standards
  name: Requirements and Standards
  description: Lloyd's market requirements and standards corpus — the primary technical surface Lloyd's publishes to its market.
- type: Documentation
  url: https://www.lloyds.com/market-resources/requirements-and-standards/core-data-record
  name: Core Data Record
  description: The Core Data Record (CDR v3.2), the market's standard transactional data set for premium validation and settlement,
    claims matching at FNOL, tax and regulatory reporting; aligned to ACORD technical standards and to the Market Reform Contract
    (MRC v3).
- type: Documentation
  url: https://www.lloyds.com/market-resources/delegated-authorities/market-knowledge/reporting-standards
  name: Coverholder and Delegated Claims Reporting Standards
  description: Mandated core reporting data set for binding authority and coverholder agreements, with premium, claims and
    ELTO reporting templates.
- type: Documentation
  url: https://www.lloyds.com/insights/news/lloyds-provides-acord-membership-for-all-coverholders
  name: ACORD Membership for Coverholders
  description: Lloyd's provides free custom ACORD membership to all coverholders, giving access to ACORD Delegated Authority
    Data Standards.
- type: GitHubOrganization
  url: https://github.com/lloydsdigital
  name: Lloyd's Digital
  description: GitHub organisation referenced by the Lloyd's API portal for the placing-api sample application; no public
    repositories — code access required a GitHub challenge through the portal.
- type: GitHubOrganization
  url: https://github.com/LloydsOfLondon
  name: Lloyd's Market Community
  description: '"A community for anyone interested in the Lloyd''s of London insurance market" — organisation exists with
    zero public repositories.'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com