Voted budgets - Special States of Arrondissements from 2018

Open data API in a single place

Provided by Direction des Finances et des Achats - Ville de Paris

Get early access to Voted budgets - Special States of Arrondissements from 2018 API!

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

Dataset information

Country of origin
Updated
2021.11.25 13:58
Created
2021.11.25
Available languages
English
Keywords
administration-et-finances-publiques, finances, dfa, budget
Quality scoring

Dataset description

The expenses and revenues of each borough council (revenues and expenses corresponding to the local facilities they manage or which are made available to them for the exercise of their powers) are detailed in a document called "special borough statement" which is annexed to the budget of the City of Paris (Article L. 2511-37 of the CGCT). The Law of 27 February 2002 also opened an investment section for the special state of each district (Article L. 2511-16(5) of the CGCT). To the exclusion of any other revenue (districts do not have the capacity to levy tax), the operating revenue of the district councils has until now been made up of a single allocation, known as the global allocation. The Law of 27 February 2002, by amending the title of the global allocation, which becomes the ‘local management’ allocation, also created a new operating allocation for district councils, namely the ‘local animation’ allocation (Article L. 2511-38 of the CGCT, as amended). The purpose of the local management allocation (ex global allocation) is therefore to enable the districts to meet the needs of the local facilities for which they are responsible. The Proximity Democracy Act also created a new allocation for local animation. The dataset shall contain, for a given financial year, all amounts voted by budget allocation. Column name | Description ---|--- Accounting year | Relevant year Arrondissement | - Budgetary Section (I/F)| Expenditure or Revenue under the Operating Section or the Investment Section Meaning (Expenditure/Revenue)| Indicates whether it is expenditure or revenue Type of operation (R/O/I/M)| Specifies whether this relates to actual expenditure (type R) or to expenditure of an order (types I/O/M). The latter do not cause any disbursement (for expenditure) or collection (for revenue) Type of Vote | This may be the Primary Budget (BP) which is annual or an infra-annual budget decision (Supplementary Budget or Amending Decision) Budgetary Chapter - Clé| Indicates the chapter number concerned according to the budget nomenclature (M57) referred to Budgetary Chapter - | Text Wording corresponding to the name of the relevant chapter of the budget nomenclature (M57) referred to Budgetary nature - | key The nature specifies the type of expenditure and the key specifies the number according to the budget nomenclature (M57) concerned Budgetary nature - | text The nature specifies the type of expenditure and the text specifies its wording according to the budget nomenclature (M57) referred to Function - | key The function indicates the destination of the expenditure and the key specifies the number according to the budget nomenclature (M57) concerned Function - Text | The function indicates the destination of the expenditure and the text specifies its wording according to the budget nomenclature (M57) referred to. Voted appropriations (pmt)| Payment appropriations constitute the upper limit of the expenditure which may be authorised during the year to cover commitments entered into under the corresponding programme authorisations.
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