Fixed Penalty Notices (FPN)

Open data API in a single place

Provided by Leeds City Council

Get early access to Fixed Penalty Notices (FPN) API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2020.11.26 16:18
Created
2017.12.18
Available languages
English
Keywords
litter, Payments, fixed penalty notice, grafitti
Quality scoring

Dataset description

This dataset shows where fixed penalty notices have been issued by Leeds City Council. It shows the amount of fine issued, how much was paid or whether it was cancelled. Fixed Penalty Notices (FPNs) are served when offenders fail to comply with a notice that has been served, e.g. waste in gardens, fly-tipping, littering, dog fouling etc. Fines are either served on the spot or by post. Column heading descriptions --------------------------- * FPN SERVED: Date when the FPN was first issued * SRRECTYPE: Code for the description (below) * SR TYPE DESC: Description of the Fixed Penalty Notice * FPN TYPE: Code which highlights the piece of legislation which the FPN relates to (see Legislation table) * TYPE DESC: Description of the piece of legislation that the FPN has been raised against (see Legislation table) * WARD: Council ward where the FPN was issued * PC: Postcode sector where the FPN was issued * FINE_DUE: The value of the FPN (see Discounts table) * FPN PAID: The actual value of the FPN paid (see Discounts table) * FPN PAID DATE: Date when the FPN was paid (see Discounts table) * PROSECUTION: Whether a court case has been launched as a result of non-payment * FPN CANCELLED: If agreed, date when the FPN was cancelled Please note ----------- * Some records use the Unique Property Reference Number (UPRN) to locate the ward. In a small number of cases this can result in the wrong ward being reported. This only occurs in relation to Service Requests on streets where the street UPRN is located in a different ward. This is not the case where Service Requests are made for a specific buildings. It should be noted that the number of these cases is very small and it is felt that as there will be discrepancies across all wards, the data still provides a balanced picture. * Where occurrences of fly tipping occur on land, e.g. in the middle of a field, a ward code may not be available due to the way the information has been historically recorded.  Other information ----------------- * **Discounts:** These are available to encourage people to pay promptly within 10 days. After this time the full amount is due, but all fines have to be paid within 14 days. On some fines no discount can be offered. See the Discounts table for more information. * **Prosecutions: **If the fines are not paid after 14 days, a reminder letter is normally sent out (which is not a statutory requirement, but a service provided by Leeds City Council). Deferred payments for people on certain benefits who may need longer to pay the fines are also offered, but proof needs to be provided first. After a reminder is sent, if the payment is not made, a case for prosecution is then prepared and the details are passed over to the council’s Legal team. Automated dataset ----------------- * This dataset is automatically updated on the 1st of each month. * The data contained within will periodically transfer to the historic dataset to aid uploading.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks