Gemeente Amsterdam

Gemeente Amsterdam (City of Amsterdam) runs the Dataplatform / DSO-API at api.data.amsterdam.nl, a public REST, WFS, MVT (vector tile) and OGC records interface over 190+ municipal datasets such as BAG addresses and buildings, area boundaries (gebieden), waste collection (afvalwijzer) and more. Each dataset publishes its own OpenAPI 3.0 document; most endpoints are anonymous, some require JWT scopes via iam.amsterdam.nl, and API keys are being introduced.

Gemeente Amsterdam publishes 21 API contracts indexed on the APIs.io network, including Acc Afvalwijzer API, Afvalwijzer API, Bouwblokken API, and 18 more. Tagged areas include Government, Open Data, Municipality, Geospatial, and Netherlands.

The Gemeente Amsterdam catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Gemeente Amsterdam’s developer surface includes authentication, documentation, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

41.2/100 developing Agent 31/100 agent ready Heartbeat 93/100 alive Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessSelf serve

3 published contracts

Government Open Data Municipality Geospatial Netherlands Addresses WFS

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 41.2/100 · developing

Contract Quality 11.9 / 21

Developer Ergonomics 5.3 / 17

Access Clarity 4.7 / 17

Operational Transparency 1.6 / 11

Contract Governance 2.2 / 10

Discoverability 6.7 / 9

Regulatory Posture 5.1 / 15

Agent readiness — 31/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Government & Public Sector regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/amsterdam-nl/"><img src="https://apis.io/badge/amsterdam-nl/card.svg" alt="Gemeente Amsterdam on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 27.7 — up to +14.5 composite points Ask about this →
Developer Ergonomics scores 31.0 — up to +13.8 composite points Ask about this →
Operational Transparency scores 14.3 — up to +11.1 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/amsterdam-nl/apis.yml: open an issue on github.com/api-evangelist/amsterdam-nl to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 21

Individual APIs this provider publishes, each with its own machine-readable definition.

Gemeente Amsterdam Acc Afvalwijzer API

The acc_afvalwijzer API from Gemeente Amsterdam — 2 operation(s) for acc_afvalwijzer.

Gemeente Amsterdam Afvalwijzer API

The afvalwijzer API from Gemeente Amsterdam — 2 operation(s) for afvalwijzer.

Gemeente Amsterdam Bouwblokken API

The bouwblokken API from Gemeente Amsterdam — 2 operation(s) for bouwblokken.

Gemeente Amsterdam Brondocumenten API

The brondocumenten API from Gemeente Amsterdam — 2 operation(s) for brondocumenten.

Gemeente Amsterdam Buurten API

The buurten API from Gemeente Amsterdam — 2 operation(s) for buurten.

Gemeente Amsterdam Dossiers API

The dossiers API from Gemeente Amsterdam — 2 operation(s) for dossiers.

Gemeente Amsterdam Ggpgebieden API

The ggpgebieden API from Gemeente Amsterdam — 2 operation(s) for ggpgebieden.

Gemeente Amsterdam Ggwgebieden API

The ggwgebieden API from Gemeente Amsterdam — 2 operation(s) for ggwgebieden.

Gemeente Amsterdam Grootstedelijke Projecten API

The grootstedelijke_projecten API from Gemeente Amsterdam — 2 operation(s) for grootstedelijke_projecten.

Gemeente Amsterdam Ligplaatsen API

The ligplaatsen API from Gemeente Amsterdam — 2 operation(s) for ligplaatsen.

Gemeente Amsterdam Nummeraanduidingen API

The nummeraanduidingen API from Gemeente Amsterdam — 2 operation(s) for nummeraanduidingen.

Gemeente Amsterdam Onderzoeken API

The onderzoeken API from Gemeente Amsterdam — 2 operation(s) for onderzoeken.

Gemeente Amsterdam Openbareruimtes API

The openbareruimtes API from Gemeente Amsterdam — 2 operation(s) for openbareruimtes.

Gemeente Amsterdam Panden API

The panden API from Gemeente Amsterdam — 2 operation(s) for panden.

Gemeente Amsterdam Stadsdelen API

The stadsdelen API from Gemeente Amsterdam — 2 operation(s) for stadsdelen.

Gemeente Amsterdam Standplaatsen API

The standplaatsen API from Gemeente Amsterdam — 2 operation(s) for standplaatsen.

Gemeente Amsterdam Stedelijkgebiedprojectofbelangen API

The stedelijkgebiedprojectofbelangen API from Gemeente Amsterdam — 2 operation(s) for stedelijkgebiedprojectofbelangen.

Gemeente Amsterdam Verblijfsobjecten API

The verblijfsobjecten API from Gemeente Amsterdam — 2 operation(s) for verblijfsobjecten.

Gemeente Amsterdam Votopafvoerlegacy API

The votopafvoerlegacy API from Gemeente Amsterdam — 2 operation(s) for votopafvoerlegacy.

Gemeente Amsterdam Wijken API

The wijken API from Gemeente Amsterdam — 2 operation(s) for wijken.

Gemeente Amsterdam Woonplaatsen API

The woonplaatsen API from Gemeente Amsterdam — 2 operation(s) for woonplaatsen.

Scroll for all 21

Gemeente Amsterdam API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Gemeente Amsterdam Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Gemeente Amsterdam Rate Limits

0 limits

RATE LIMITS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Amsterdam Nl Context

120 classes · 217 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Gemeente Amsterdam API Rules

52 rules · 44 error-severity 6 warn-severity 2 info-severity

SPECTRAL

JSON Schema 16

Standalone JSON Schema definitions for this provider's data models.

Afvalwijzeracc_afvalwijzer

43 properties

JSON SCHEMA

Afvalwijzerafvalwijzer

44 properties

JSON SCHEMA

Bagligplaatsen

20 properties

JSON SCHEMA

Bagnummeraanduidingen

28 properties

JSON SCHEMA

Bagopenbareruimtes

26 properties

JSON SCHEMA

Bagpanden

27 properties

JSON SCHEMA

Bagstandplaatsen

20 properties

JSON SCHEMA

Bagverblijfsobjecten

44 properties

JSON SCHEMA

Gebiedenbouwblokken

9 properties

JSON SCHEMA

Gebiedenbuurten

15 properties

JSON SCHEMA

Gebiedenggpgebieden

12 properties

JSON SCHEMA

Gebiedenggwgebieden

12 properties

JSON SCHEMA

Gebiedenstadsdelen

12 properties

JSON SCHEMA

Gebiedenwijken

14 properties

JSON SCHEMA

PaginatedAfvalwijzeracc_afvalwijzerList

3 properties

JSON SCHEMA

PaginatedAfvalwijzerafvalwijzerList

3 properties

JSON SCHEMA

Scroll for all 16

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Gemeente Amsterdam Authentication

oauth2 · 1 scheme

SECURITY

Gemeente Amsterdam Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Gemeente Amsterdam Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Gemeente Amsterdam Agentic Access

42 operations

42 operations · 0 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

OpenAPI

OpenAPI

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

WellKnown

WellKnown

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conventions

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 4

Authentication, authorization, and security posture

SecurityTxt

Authentication

DomainSecurity

Authentication

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: amsterdam-nl
name: Gemeente Amsterdam
description: Gemeente Amsterdam (City of Amsterdam) runs the Dataplatform / DSO-API at api.data.amsterdam.nl, a public REST,
  WFS, MVT (vector tile) and OGC records interface over 190+ municipal datasets such as BAG addresses and buildings, area
  boundaries (gebieden), waste collection (afvalwijzer) and more. Each dataset publishes its own OpenAPI 3.0 document; most
  endpoints are anonymous, some require JWT scopes via iam.amsterdam.nl, and API keys are being introduced.
url: https://artifacts.apis.io/amsterdam-nl/apis.yml
x-type: company
x-source: harvest:eu-gov-keynote-2026-11-10
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-10 (local-v6; was harvest)
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: low
  probe_state: covered
  source:
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
specificationVersion: '0.20'
created: '2026-11-10'
modified: '2026-11-10'
tags:
- Government
- Open Data
- Municipality
- Geospatial
- Netherlands
- Addresses
- WFS
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgenticAccess
  url: agentic-access/amsterdam-nl-agentic-access.yml
- type: Spectral
  url: rules/amsterdam-nl-rules.yml
- type: JSONLD
  url: json-ld/amsterdam-nl-context.jsonld
- type: Vocabulary
  url: vocabulary/amsterdam-nl-vocabulary.yml
- type: DataModel
  url: data-model/amsterdam-nl-data-model.yml
- type: Conventions
  url: conventions/amsterdam-nl-conventions.yml
- type: Conformance
  url: conformance/amsterdam-nl-conformance.yml
- type: SecurityTxt
  url: well-known/amsterdam-nl-security.txt
- type: WellKnown
  url: well-known/amsterdam-nl-well-known.yml
- type: Hosts
  url: hosts/amsterdam-nl-hosts.yml
- type: Vendors
  url: vendors/amsterdam-nl-vendors.yml
- type: Authentication
  url: authentication/amsterdam-nl-authentication.yml
- type: DomainSecurity
  url: security/amsterdam-nl-domain-security.yml
- type: Website
  url: https://www.amsterdam.nl/
- type: DeveloperPortal
  url: https://api.data.amsterdam.nl/v1/
- type: Documentation
  url: https://api.data.amsterdam.nl/v1/docs/
- type: Authentication
  url: https://api.data.amsterdam.nl/v1/docs/generic/rest/authorization.html
  name: Authorization docs
- type: OpenAPI
  name: Combined DSO-API OpenAPI (1255 operations)
  url: https://api.data.amsterdam.nl/v1/openapi.json
- type: GitHubOrganization
  url: https://github.com/Amsterdam
- type: Login
  url: https://app.amsterdam.nl/
- type: PrivacyPolicy
  url: https://app.amsterdam.nl/privacyverklaring/
- type: TermsOfService
  url: https://data.amsterdam.nl/
apis:
- aid: amsterdam-nl:amsterdam-nl-acc-afvalwijzer-api
  name: Gemeente Amsterdam Acc Afvalwijzer API
  description: The acc_afvalwijzer API from Gemeente Amsterdam — 2 operation(s) for acc_afvalwijzer.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags: []
  tags_raw:
  - acc_afvalwijzer
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-acc-afvalwijzer-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-afvalwijzeracc-afvalwijzer-schema.json
  - type: JSONSchema
    url: json-schema/amsterdam-nl-paginated-afvalwijzeracc-afvalwijzer-list-schema.json
- aid: amsterdam-nl:amsterdam-nl-afvalwijzer-api
  name: Gemeente Amsterdam Afvalwijzer API
  description: The afvalwijzer API from Gemeente Amsterdam — 2 operation(s) for afvalwijzer.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - afvalwijzer
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-afvalwijzer-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-afvalwijzerafvalwijzer-schema.json
  - type: JSONSchema
    url: json-schema/amsterdam-nl-paginated-afvalwijzerafvalwijzer-list-schema.json
- aid: amsterdam-nl:amsterdam-nl-bouwblokken-api
  name: Gemeente Amsterdam Bouwblokken API
  description: The bouwblokken API from Gemeente Amsterdam — 2 operation(s) for bouwblokken.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - bouwblokken
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-bouwblokken-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-gebiedenbouwblokken-schema.json
- aid: amsterdam-nl:amsterdam-nl-brondocumenten-api
  name: Gemeente Amsterdam Brondocumenten API
  description: The brondocumenten API from Gemeente Amsterdam — 2 operation(s) for brondocumenten.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - brondocumenten
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-brondocumenten-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
- aid: amsterdam-nl:amsterdam-nl-buurten-api
  name: Gemeente Amsterdam Buurten API
  description: The buurten API from Gemeente Amsterdam — 2 operation(s) for buurten.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - buurten
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-buurten-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-gebiedenbuurten-schema.json
- aid: amsterdam-nl:amsterdam-nl-dossiers-api
  name: Gemeente Amsterdam Dossiers API
  description: The dossiers API from Gemeente Amsterdam — 2 operation(s) for dossiers.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - Dossiers
  tags_raw:
  - dossiers
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-dossiers-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
- aid: amsterdam-nl:amsterdam-nl-ggpgebieden-api
  name: Gemeente Amsterdam Ggpgebieden API
  description: The ggpgebieden API from Gemeente Amsterdam — 2 operation(s) for ggpgebieden.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - ggpgebieden
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-ggpgebieden-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-gebiedenggpgebieden-schema.json
- aid: amsterdam-nl:amsterdam-nl-ggwgebieden-api
  name: Gemeente Amsterdam Ggwgebieden API
  description: The ggwgebieden API from Gemeente Amsterdam — 2 operation(s) for ggwgebieden.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - ggwgebieden
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-ggwgebieden-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-gebiedenggwgebieden-schema.json
- aid: amsterdam-nl:amsterdam-nl-grootstedelijke-projecten-api
  name: Gemeente Amsterdam Grootstedelijke Projecten API
  description: The grootstedelijke_projecten API from Gemeente Amsterdam — 2 operation(s) for grootstedelijke_projecten.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags: []
  tags_raw:
  - grootstedelijke_projecten
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-grootstedelijke-projecten-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
- aid: amsterdam-nl:amsterdam-nl-ligplaatsen-api
  name: Gemeente Amsterdam Ligplaatsen API
  description: The ligplaatsen API from Gemeente Amsterdam — 2 operation(s) for ligplaatsen.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - ligplaatsen
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-ligplaatsen-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-bagligplaatsen-schema.json
- aid: amsterdam-nl:amsterdam-nl-nummeraanduidingen-api
  name: Gemeente Amsterdam Nummeraanduidingen API
  description: The nummeraanduidingen API from Gemeente Amsterdam — 2 operation(s) for nummeraanduidingen.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - nummeraanduidingen
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-nummeraanduidingen-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-bagnummeraanduidingen-schema.json
- aid: amsterdam-nl:amsterdam-nl-onderzoeken-api
  name: Gemeente Amsterdam Onderzoeken API
  description: The onderzoeken API from Gemeente Amsterdam — 2 operation(s) for onderzoeken.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - onderzoeken
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-onderzoeken-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
- aid: amsterdam-nl:amsterdam-nl-openbareruimtes-api
  name: Gemeente Amsterdam Openbareruimtes API
  description: The openbareruimtes API from Gemeente Amsterdam — 2 operation(s) for openbareruimtes.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - openbareruimtes
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-openbareruimtes-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-bagopenbareruimtes-schema.json
- aid: amsterdam-nl:amsterdam-nl-panden-api
  name: Gemeente Amsterdam Panden API
  description: The panden API from Gemeente Amsterdam — 2 operation(s) for panden.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - panden
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-panden-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-bagpanden-schema.json
- aid: amsterdam-nl:amsterdam-nl-stadsdelen-api
  name: Gemeente Amsterdam Stadsdelen API
  description: The stadsdelen API from Gemeente Amsterdam — 2 operation(s) for stadsdelen.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - stadsdelen
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-stadsdelen-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-gebiedenstadsdelen-schema.json
- aid: amsterdam-nl:amsterdam-nl-standplaatsen-api
  name: Gemeente Amsterdam Standplaatsen API
  description: The standplaatsen API from Gemeente Amsterdam — 2 operation(s) for standplaatsen.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - standplaatsen
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-standplaatsen-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-bagstandplaatsen-schema.json
- aid: amsterdam-nl:amsterdam-nl-stedelijkgebiedprojectofbelangen-api
  name: Gemeente Amsterdam Stedelijkgebiedprojectofbelangen API
  description: The stedelijkgebiedprojectofbelangen API from Gemeente Amsterdam — 2 operation(s) for stedelijkgebiedprojectofbelangen.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - stedelijkgebiedprojectofbelangen
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-stedelijkgebiedprojectofbelangen-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
- aid: amsterdam-nl:amsterdam-nl-verblijfsobjecten-api
  name: Gemeente Amsterdam Verblijfsobjecten API
  description: The verblijfsobjecten API from Gemeente Amsterdam — 2 operation(s) for verblijfsobjecten.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - verblijfsobjecten
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-verblijfsobjecten-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-bagverblijfsobjecten-schema.json
- aid: amsterdam-nl:amsterdam-nl-votopafvoerlegacy-api
  name: Gemeente Amsterdam Votopafvoerlegacy API
  description: The votopafvoerlegacy API from Gemeente Amsterdam — 2 operation(s) for votopafvoerlegacy.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - votopafvoerlegacy
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-votopafvoerlegacy-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
- aid: amsterdam-nl:amsterdam-nl-wijken-api
  name: Gemeente Amsterdam Wijken API
  description: The wijken API from Gemeente Amsterdam — 2 operation(s) for wijken.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - wijken
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-wijken-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
  - type: JSONSchema
    url: json-schema/amsterdam-nl-gebiedenwijken-schema.json
- aid: amsterdam-nl:amsterdam-nl-woonplaatsen-api
  name: Gemeente Amsterdam Woonplaatsen API
  description: The woonplaatsen API from Gemeente Amsterdam — 2 operation(s) for woonplaatsen.
  humanURL: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  baseURL: https://api.data.amsterdam.nl/
  tags:
  - woonplaatsen
  properties:
  - type: OpenAPI
    url: openapi/amsterdam-nl-woonplaatsen-api-openapi.yml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/gebieden.html
  - type: GetCapabilities
    url: capabilities/amsterdam-nl-gebieden-wfs-capabilities.xml
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/bag.html
  - type: Documentation
    url: https://api.data.amsterdam.nl/v1/docs/datasets/afvalwijzer.html
x-enrichment:
  date: '2026-11-10'
  status: enriched
  artifacts_added: 14
  pass: local-v6
x-coverage:
  state: covered
  reason: covered
  detail: DSO-API publishes per-dataset OpenAPI and WFS capabilities.
  evidence:
  - url: https://api.data.amsterdam.nl/v1/gebieden/openapi.json
    status: 200
  checked: '2026-11-10'

Gemeente Amsterdam API — frequently asked questions

Does Gemeente Amsterdam have an API?

Yes. APIs.io lists 21 APIs from Gemeente Amsterdam, including Gemeente Amsterdam Acc Afvalwijzer API, Gemeente Amsterdam Afvalwijzer API and Gemeente Amsterdam Bouwblokken API, and 18 more.

Is there an OpenAPI specification for the Gemeente Amsterdam API?

Yes. APIs.io indexes 21 OpenAPI specifications for Gemeente Amsterdam, each linked for download from this page.

How do I authenticate with the Gemeente Amsterdam API?

Gemeente Amsterdam uses bearer-token authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Gemeente Amsterdam Authentication.

Is the Gemeente Amsterdam API ready for AI agents?

Gemeente Amsterdam has a Kin Score of 41.2 out of 100 (developing) and an Agent Readiness score of 30.5 (agent-ready), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/amsterdam-nl"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/amsterdam-nl/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/amsterdam-nl/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.