Belgium DATEX II API

Introduction

Use the Eco-Movement Belgium DATEX II API to retrieve public charge-point data for Belgium, including static location data and dynamic EVSE status and price data.

The API is an outbound API based on the DATEX II v3 standard. It supports Belgium's national access point, transportdata.be, and aligns with AFIR Article 20. It uses RESTful web-service architecture and returns JSON-encoded responses.

Base URL

https://nap-be.eco-movement.com

Authorization

Add an Authorization header to every HTTP request:

Authorization: Bearer <token>

The Bearer scheme uses token-based authentication. The token is a string of printable, non-whitespace ASCII characters that uniquely identifies you.

To request a token, email [email protected].

Endpoints

Method	Path	Description
`GET`	`/datex2/v1/locations`	Returns the full static snapshot for Belgium: locations, EVSEs, connectors, technical characteristics, operators, and access information. The snapshot refreshes every 24 hours.
`GET`	`/datex2/v1/status/{evse_id}`	Returns dynamic availability/status and the ad-hoc price for a single EVSE. Data updates on change, within one minute.

Example:

GET https://nap-be.eco-movement.com/datex2/v1/status/BEALLEG00002081

The /locations endpoint returns the complete country snapshot in one response; it is not paginated.

Data follows the same DATEX II JSON mapping as the German NAP feed. Belgium has no published country-specific DATEX II profile, so field mapping follows the generic DATEX II v3 AFIR standard.

Supported methods

Method	Description
`GET`	Fetch objects or information.

Rate limits

Every request must satisfy both rate limits.

Per token

Endpoint	Limit
`/datex2/v1/status/{evse_id}`	2 requests per minute, per EVSE
`/datex2/v1/locations`	30 requests per hour

Per IP address

You can make 1 request every 10 seconds across all endpoints.

Requests that exceed either limit receive an HTTP 429 response. Check the rate-limit headers on the response to see when you can retry.