FCA Handbook API: How to Query UK Rules Programmatically

On 6 August 2026, the Financial Conduct Authority began serving its Handbook of rules and guidance through a new application programming interface. The FCA Handbook API lets a firm’s own software pull the text of UK conduct rules, technical standards and defined terms directly, instead of reading them off the website or waiting for a monthly download. The FCA describes the change as part of being a smarter regulator, and its 6 August blog by Alex Smith, Head of Cross-cutting Policy & Strategy, gives examples of how firms and technology providers may use it.

For a compliance or reporting team, the useful question is which parts of your rule-mapping and change-management workflow can safely consume a live feed, and which still need a retained, point-in-time record and a human reading. Machine-readable rules are plainly useful; the design work is in drawing that line. The API is free to access through a registered Handbook account. It extracts the latest Handbook content, gives access to current and future versions, and does not provide past versions; firms remain responsible for interpreting and applying the content.

The Handbook is a key source for determining how a firm’s regulatory status and permissions affect SUP reporting requirements and how Glossary definitions drive a return; the permissions the firm actually holds, including any limitations or requirements, must be confirmed from its current authorisation record and the Financial Services Register. Moving current consolidated Handbook text into a queryable feed changes how regulatory text enters your control stack; it does not make the API response the definitive legal text. It also raises a governance question about versioning before a firm builds anything on top of it.

Related reading: our guide to the FCA’s MiFIR transaction reporting reform (PS26/15).

What is live, and since when

A short calendar helps before the detail, because the API and the website behind it arrived in stages:

• 4 July 2025: the FCA announced a new and improved Handbook website, with tools to navigate rules, see their connections and compare versions; the legacy site remained available for a short transition period before full launch.
• 6 August 2026: the FCA announced that Handbook data is now available directly through the new API.
• Cost: the API is available to any user who has registered for a free account on the Handbook website, at no charge.
• Content: the API exposes Handbook data, Technical Standards data and Glossary data.
• Versions: it extracts content from the latest version of the Handbook, and the FCA also points to current and future versions for tracking changes. It does not provide past versions of Handbook content.
• Access tooling: the FCA points registered users to standard API clients such as Postman or RapidAPI to interact with it.

Every operational decision below follows from that list, so it is worth pinning it somewhere your build team can see it.

What the FCA Handbook API actually exposes

The FCA Handbook contains rules and guidance made under FSMA 2000 and other statutory powers. Section 137A is the FCA’s general rule-making power and section 139A its general guidance power, but individual Handbook instruments may rely on other FSMA provisions or sector-specific legislation. The API covers sourcebooks including SYSC, SUP, COBS and REC, plus the Glossary; reporting and notification obligations may also sit elsewhere in the Handbook, Technical Standards, legislation or the PRA Rulebook.

The API is documented as covering three data sets: Handbook data, Technical Standards data and Glossary data. Technical Standards are presented separately from Handbook sourcebooks, but they are not one uniform legal category. The FCA Handbook site includes both technical standards derived from EU measures and standards made under UK powers; each instrument’s legal basis, current status and responsible regulator must be checked before it is mapped to an obligation.

The Glossary being its own data set is the quiet win here. Where a firm applies the ordinary meaning of a word that the Glossary defines narrowly, the result is a mis-stated return, and that failure mode is easy to miss because the word looks familiar. Pulling the Glossary as structured data lets a firm bind its internal control descriptions to the exact defined term, and re-check them automatically when that definition changes.

How access works in practice

Access starts with a free account on the Handbook website. The FCA states that the API is available to registered users subject to the Terms and Conditions, and names external applications such as Postman or RapidAPI for interaction. Free access does not grant unrestricted storage or reuse. The Handbook Terms and Conditions state that users must not reproduce or store any part of the site in another website or include it in a public or private electronic retrieval system or service without prior written permission. They also state that reproducing more than 20,000 words from the FCA Handbook requires a Handbook Licence Agreement.

The FCA states that protected endpoints are rate-limited per authenticated user and endpoint path, but its public FAQ does not state the numerical limits. Verify the authenticated API documentation and account terms before selecting a service-account, concurrency or mirroring model. Design for rate-limit errors and retry/backoff rather than assuming that a nightly full-Handbook pull or shared account will stay within the limit.

The FCA also flags that registered users are enrolled in a monthly Handbook updates mailing list. That monthly update channel is worth keeping as an FCA-issued notification and a cross-check against any automated diff; the public FAQ does not describe the format or level of narrative detail in those updates.

The latest-version rule, and why point-in-time evidence is your job

Here is the boundary most firms will trip over. The FCA says the API automatically extracts content from the latest version of the Handbook, and separately that it does not provide past versions of Handbook content. The 6 August blog talks about access to current and future versions helping firms track, compare and flag rule updates. Read those together and the picture is consistent: you can see the text as it stands now, and forthcoming versions the FCA has already published with a future commencement date, but not the Handbook as it read on some date in the past.

That gap is a design constraint you have to plan for. Reporting and compliance work routinely needs an as-was position: what did the rule say on the reporting reference date, what applied at the time of a transaction now under review, what text supported a control that a skilled person is testing two years later. The website provides version-comparison and archive tools, while the API provides no past versions. A firm needing a reproducible API-based history therefore needs an alternative evidenced source or, subject to the FCA’s reuse terms, its own retained records.

Subject to the FCA Handbook Terms and Conditions and any required permission or licence, a firm may retain evidence of the Handbook content it consumed, the retrieval date and any version or effective-date metadata actually exposed by the API. Do not assume that the API returns a specific version identifier or that a full point-in-time repository is permitted until the authenticated API documentation and reuse terms have been checked.

What machine-readable rules will not do for you

The FCA is candid that technology will not solve every compliance challenge on its own, and the wording repays attention. The API delivers the text of the rules in a structured form. Determining which rules apply to a firm’s permissions, how a principle-based provision bears on a specific product, or whether a reading of ambiguous guidance would survive supervisory scrutiny remains the work of interpretation, and interpretation stays with the firm and its advisers.

This is where a data feed can create a false sense of completeness. A pipeline that ingests the full Handbook and flags every change looks thorough on a dashboard, yet a change to a sourcebook you are not subject to is noise, and a subtle Glossary tweak that quietly widens a term you do rely on can pass unremarked if nobody has mapped that term to a control. The value comes from binding the specific provisions you are subject to, by permission and business line, to the controls and returns they drive, and then letting the feed tell you when those provisions move. Ingesting everything just relocates the noise.

The FCA’s Legal Information states that the definitive Handbook text at any particular time is the text contained in the FCA legal instruments, including amending instruments, published on the FCA website. An API response and the consolidated webpage are access formats. If they appear to diverge, verify the applicable legal instrument rather than assuming that either display format prevails.

Where the API fits a reporting and change-management workflow

The FCA’s blog names four uses, and each maps onto something a reporting or compliance team already does by hand.

Rule mapping

The FCA suggests the data may help firms map rules to products, activities and customer journeys, so that the impact of a change is easier to assess. For a reporting team this is the mapping between a SUP reporting requirement and the internal process that produces the return, or between a permission and the data items a supervisor expects. Built once against structured data and keyed to the Glossary, that map can be re-run when the underlying text changes, instead of being rebuilt from scratch each time someone notices a rule has moved.

Tracking rule changes

Access to current and future versions is meant to help firms track, compare and flag rule updates and respond more quickly. This is horizon scanning turned into a service call. The practical benefit is lead time: because the API includes forthcoming versions the FCA has already published, a change-management function can pick up a future-dated amendment as soon as it is in the Handbook, rather than discovering it in a monthly Handbook update. The caveat from the previous section still holds, because the historic side of any comparison has to come from your own retained records, subject to the FCA’s reuse terms.

Better RegTech products

The FCA expects technology providers and RegTech firms to build on the data, giving them authoritative Handbook content to develop more consistent compliance tools. For a firm that buys its tooling, the question to put to a vendor becomes concrete: is your product now sourced from the FCA Handbook API, how often does it refresh, and how do you retain the historic versions the API does not serve. Our coverage of RegTech innovation lessons from the ASIC and DFCRC work sets out why the provenance of the underlying rule data is the right thing to interrogate.

Supporting AI tools

The FCA frames the API as providing trusted, up-to-date data to support more useful, accurate and transparent AI tools. The FCA says the API provides trusted, up-to-date data that may support more useful, accurate and transparent AI tools, but it does not claim that the feed prevents fabricated citations or guarantees accuracy. Firms must determine which existing FCA rules apply to an AI use case and govern the resulting risks; the linked EU AI Act article is not a statement of UK legal requirements.

The PRA Rulebook boundary, and other scope edges

A dual-regulated firm should read the label carefully. This is the FCA Handbook API. The Prudential Regulation Authority maintains a separate PRA Rulebook. PRA rules for PRA-regulated banks, building societies, credit unions, insurers and major investment firms are not part of the FCA Handbook API, although those firms remain subject to relevant FCA Handbook requirements. Our note on the PRA’s restatement of CRR definitions into the PRA Rulebook is a reminder that, after the repeal and replacement of assimilated law, the same subject can now sit in different rulebooks depending on which regulator owns it. Mapping an obligation to the wrong rulebook is a classic dual-regulation error, and a machine-readable feed applies the map faster, and any mis-scoped obligation reaches the wrong place with it.

Two further edges are worth naming, without cataloguing every scope boundary. First, the API carries Handbook rules, technical standards and glossary terms, not the FCA’s supervisory correspondence, Dear CEO letters, or portal specifications, so the operational detail of how a return is actually submitted still lives outside it. Second, the SYSC and SUP text you pull states what is required, not what your firm has implemented; the mapping from rule to control remains a firm artifact. For the accountability rules that sit across SYSC and SUP, our write-up of the 2026 SM&CR reforms shows how tightly those sourcebooks interlock.

A smarter regulator, and the growth objective behind it

The API is filed by the FCA under its growth agenda, and that context is real. Since 29 August 2023, the FCA has had a secondary objective under FSMA to facilitate the international competitiveness and medium-to-long-term growth of the UK economy, subject to aligning with relevant international standards. The FCA presents the API as a way to make regulatory information easier to use, reduce manual processes and support growth. Reading the release that way sets expectations correctly: the launch materials describe an access and tooling improvement and do not announce amendments to reporting obligations or deadlines.

The 6 August announcement covers structured, machine-readable Handbook access. It makes no commitment on machine-executable rules, a reporting-submission API or a wider cross-jurisdiction programme.

Frequently Asked Questions

Does the Handbook API replace RegData or any reporting submission channel?

No. The FCA’s public materials describe the Handbook API as a way to access Handbook, Technical Standards and Glossary data. RegData remains the FCA platform for submitting regulatory data; the launch materials do not describe the Handbook API as a return-submission or validation channel.

Can I pull the Handbook as it read on a past date, for an as-was compliance position?

Not from the API. The FCA states that the API extracts the latest Handbook content, provides no past versions, and gives an error for past-date requests. The website provides version-comparison and archive tools. A firm that needs its own API-based historical evidence should first confirm that the proposed storage is permitted under the FCA Handbook Terms and Conditions and obtain any required permission or licence.

Is there a cost, and does a RegTech vendor need a different licence?

The FCA describes the API as available to any user with a free registered Handbook account, subject to accepting the Terms and Conditions. Those terms govern how the data may be used and redistributed, so a vendor building a commercial product on the feed should read the conditions on reuse before assuming the free access point implies an unrestricted commercial licence.

Does it include the PRA Rulebook?

No. The API does not include the PRA Rulebook. PRA rules for PRA-regulated firms must be sourced separately, while relevant FCA Handbook requirements continue to apply.

Are the technical standards in the API the same as the onshored EU RTS and ITS?

The API exposes Technical Standards data as a distinct set from Handbook rules. The Technical Standards data set is not one uniform category of assimilated EU RTS and ITS: the FCA Handbook site includes standards derived from EU measures and standards made under UK powers. Confirm the specific instrument and its current status before treating an API extract as the operative standard, because responsibility for a given standard can sit with the FCA, the PRA or the Bank of England.

How should we handle rate limits for a full-Handbook ingestion?

The FCA states that protected endpoints are rate-limited per authenticated user and endpoint path. The public FAQ does not disclose numerical rate limits or compare throttling scenarios. Verify the authenticated API documentation, then design for rate-limit errors, controlled concurrency and retry/backoff.

Is an API extract legally the rules, or just a copy?

The FCA’s Legal Information states that the definitive Handbook text at any particular time is contained in the applicable FCA legal instruments, including amending instruments, published on the FCA website. If an API response and consolidated webpage appear to differ, verify the instrument and record the retrieval date and any version metadata actually exposed by the API.

Related Articles

• UK MiFIR Transaction Reporting Reform (PS26/15): how the FCA is reshaping the transaction reporting regime the Handbook and technical standards govern.
• SM&CR Reforms 2026: the accountability changes that run through the SYSC and SUP sourcebooks you can now pull via the API.
• PRA CRR Definitions Restatement: why prudential rules sit in the separate PRA Rulebook and not the FCA Handbook.
• ASIC and DFCRC RegTech Innovation: lessons on why the provenance of rule data matters when a tool automates compliance.
• UK Critical Third Parties Oversight Regime: the governance frame for relying on external technology providers in UK financial services.

Key Takeaways

• The FCA Handbook API went live on 6 August 2026, serving Handbook rules, technical standards and glossary terms in a structured, machine-readable form.
• Access is free but gated: register for a free Handbook website account and accept the Terms and Conditions before use.
• The API provides current and future Handbook content but no past versions. Use the Handbook’s version tools or, subject to the Terms and Conditions and any required permission or licence, retain evidence of the content your systems consumed.
• Protected endpoints are rate-limited per authenticated user and endpoint path, so build a scheduled ingestion service with backoff.
• Bind the specific provisions you are subject to, by permission and business line, to your controls and returns; ingesting everything just relocates the noise.
• The API covers FCA Handbook, Technical Standards and Glossary data; it does not include the separate PRA Rulebook.
• The API supplies regulatory data. Firms remain responsible for interpreting and applying relevant requirements, and any AI use remains subject to the existing FCA rules and governance arrangements applicable to that use case.
• The launch materials describe an access and tooling improvement; they do not announce amendments to reporting obligations or deadlines.

Sources and References

• FCA blog, “Making compliance simpler: opening up the FCA Handbook through our new API” (6 August 2026): fca.org.uk/news/blogs/making-compliance-simpler-opening-fca-handbook-new-api
• FCA Handbook API FAQs and access notes: handbook.fca.org.uk (Handbook API news and FAQs)
• FCA Handbook API documentation page (Handbook, Technical Standards and Glossary data): handbook.fca.org.uk/handbook-api
• FCA news, “A new improved Handbook website” (first published 4 July 2025): fca.org.uk/news/news-stories/new-improved-handbook-website
• Financial Services and Markets Act 2000 (FCA rule-making power, section 137A; guidance, section 139A): legislation.gov.uk/ukpga/2000/8
• FCA Legal Information (definitive Handbook text; storage and reproduction terms): fca.org.uk/legal
• FCA Handbook (the authoritative rulebook): handbook.fca.org.uk

Wiring the feed in without over-trusting it

The integration requires a registered account and a controlled ingestion design, but a full snapshot repository is not automatically authorised by free access. Confirm the authenticated API documentation and the FCA Handbook Terms and Conditions, obtain any required permission or licence for storage and reuse, and then map the applicable sourcebooks, technical standards and Glossary terms to controls and returns with human review before reporting action. Do that, and the next time a SUP requirement or a defined term shifts, your team sees it in the feed with the affected provisions already mapped, before the change has to be chased down from a monthly Handbook update.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.