Co. Mayo Municipal Districts

Open data API in a single place

Provided by Mayo County Council

Get early access to Co. Mayo Municipal Districts API!

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

Dataset information

Catalog

Mayo County Council catalog

Country of origin

Ireland

Updated

2024.11.05 11:45

Created

2014.06.30

Available languages

English

Keywords

castlebar, local authority, science, society, municipal level, ballina, geography, administrative units, claremorris, politics, atmosphere, administration, mayo, administrative organisation, boundaries, government, political organisation

Datasource

Official portal for European data link

Quality scoring

Dataset description

A municipal district is an administrative entity comprising a clearly defined territory and its population. It can refer to a city, town, village or a small grouping of them, or a rural area. Following the Putting People First, Action Programme for Local Government and the Local Government Reform Act 2014, County Mayo's former six Electoral Areas were re-structured as four Municipal Districts: West Mayo, Castlebar, Ballina and Claremorris. Municipal Districts for the new tier of local governance at sub-county level. The first election to the new Municipal Districts was in June 2014, where councillors were elected simultaneously in local electoral areas to both a Municipal Districts and County Council.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.

api.store Built by Apitalks

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

About api.storePrivacy Terms of Service