Can the FCA Handbook API make compliance simpler?

The new FCA Handbook application programming interface (API) gives firms and technology providers direct access to structured, machine-readable regulatory content. It could reduce manual monitoring and improve rule mapping, but it does not interpret the rules or decide how they apply. Firms remain responsible for regulatory judgement, governance and implementation.

API

The FCA has made its Handbook available directly through an API (Application Programming Interface). Launched on the 6th August 2026, the API allows regulated financial services firms to retrieve FCA Handbook rules, guidance, technical standards and its glossary in a structured format that other applications can use. Until now, firms have accessed the Handbook through the website, monthly downloads or specialist compliance products. Now, firms that have suitable technology can connect the Handbook to their own systems – or alternatively use tools created by RegTech providers. 

How can the FCA’s Handbook API help compliance teams?

Regulatory change can involve significant manual work, from identifying relevant updates to assessing their impact and making sure changes are implemented. The API could streamline parts of this process by allowing firms to map Handbook provisions to products, permissions, policies, controls and customer journeys.  

It may also help them compare current and future content and identify relevant changes earlier. Access to trusted, current data could make these tools more reliable and create clearer links between regulatory requirements and day-to-day operations. The benefit, however, will depend on the quality of the firm’s underlying processes, data and governance. 

How can the FCA’s Handbook API be implemented?

Firms may choose to begin with their regulatory change process rather than technology. This means looking at where Handbook monitoring, regulatory analysis or rule mapping remains manual, repetitive or difficult to evidence. That assessment can help identify a specific use case rather than treating the API as a technology project in its own right. For example, a firm could connect a limited set of Handbook provisions to relevant products, policies, controls and customer journeys – it could then test how an update is identified, assessed, allocated and recorded. 

A focused pilot will help firms see whether the API improves speed and consistency without weakening oversight or accountability. But it’s important to consider governance from the outset as firms will need to decide: 

  • who owns the connection 
  • who checks the data 
  • how exceptions are handled and when compliance or legal approval is required 

Not every firm will need to build a direct connection. Some may work with a provider, while others may decide that the Handbook website and their existing monitoring arrangements remain suitable. The right approach will depend on the firm’s size, regulatory exposure and technical capability. 

Supporting sources

  1. Making compliance simpler: opening up the FCA Handbook through our new API
  2. Launch of Handbook API

Frequently asked questions

What is the FCA Handbook API?

It is a service that gives registered users structured, machine-readable access to FCA Handbook, technical standards and glossary content for use in compatible software applications. 

Is use of the Handbook API compulsory?

No. Firms can connect to it directly, use a technology provider or continue to use the Handbook website and their existing compliance tools. 

Does the API interpret FCA rules?

No. It provides structured regulatory content, but firms remain responsible for deciding which requirements apply and how they should be implemented. 

Does the API include historic Handbook versions?

No. It provides current and future versions, but not past versions. Firms may need their own process for retaining point-in-time evidence. 

Reviewed by TCC Group Editorial Team

Ready to strengthen your compliance?

Speak to our experts about your regulatory challenges.