# AFIR access

# AFIR Endpoint Access

:::warning{title="This endpoint is deprecated — use the Public API instead"}

The Monta API AFIR endpoint is **deprecated** and will be **sunset on 8 September 2026**. A new, **DATEX II–compliant** AFIR endpoint is now available in the **Monta Public API**:

* **List AFIR-compliant charge points** → [docs.public-api.monta.com/reference/get-afir-charge-points](https://docs.public-api.monta.com/reference/get-afir-charge-points)
* **Get EVSE dynamic status** → [docs.public-api.monta.com/reference/get-afir-evse-status](https://docs.public-api.monta.com/reference/get-afir-evse-status)

This is **not a drop-in swap** — see [Migrating to the Public API](#-migrating-to-the-public-api) below.

:::

The **AFIR endpoint** exposes publicly accessible static and dynamic data from Monta charge points, as required by **Article 20 of the AFIR regulation**. This includes metadata like location, connector types, power levels, status, availability, and ad hoc pricing.

> The goal is to promote transparency, accessibility, and interoperability across the EU's alternative fuels infrastructure.

***

## 🔁 Migrating to the Public API

The replacement endpoint lives in the [Monta Public API](https://docs.public-api.monta.com/reference/home), not this API. Migrating involves more than changing a URL:

| Aspect          | Old — Monta API (deprecated)                   | New — Public API                                           |
| --------------- | ---------------------------------------------- | ---------------------------------------------------------- |
| Endpoint        | `GET /api/v1/afir/charge-points`               | `GET /api/v1/afir/charge-points`                           |
| Host            | `partner-api.monta.com`                        | `public-api.monta.com`                                     |
| Authentication  | Monta API consumer `clientId` / `clientSecret` | Public API **application** credentials (separate app)      |
| Response format | Custom Monta JSON                              | **DATEX II** (`EnergyInfrastructureTablePublication`)      |
| Country filter  | `countryId` (numeric)                          | `country` (ISO 3166-1 alpha-2, e.g. `DK`, `BE`)            |
| Pagination      | Cursor-based (`after` / `before`)              | Offset-based (`page` / `perPage`)                          |
| Dynamic status  | Included per charge point                      | Dedicated endpoint (`/afir/charge-points/{evseId}/status`) |

To migrate:

1. **Get access and authenticate.** The Public API [Authentication guide](https://docs.public-api.monta.com/reference/authentication) explains how to obtain access and request an access token — start there.
2. Switch to the [List AFIR-compliant charge points](https://docs.public-api.monta.com/reference/get-afir-charge-points) endpoint and map the DATEX II response.
3. For live availability and ad hoc pricing, call [Get EVSE dynamic status](https://docs.public-api.monta.com/reference/get-afir-evse-status) with the OCPI EVSE identifier (e.g. `DK*MON*E100001`).

***

## Legacy: Monta API AFIR endpoint (deprecated)

:::warning

The endpoints below are **deprecated** and retained for existing consumers only until **8 September 2026**. New integrations should use the [Public API endpoint](https://docs.public-api.monta.com/reference/get-afir-charge-points).

:::

### 🔐 How to Obtain an Access Token

Existing consumers are provisioned with a `clientId` and a `clientSecret`. Obtain your access token by following this guide: [https://docs.partner-api.monta.com/reference/ref-authentication](/reference/ref-authentication)

### 📚 API Reference

The deprecated AFIR endpoint is documented here: [https://docs.partner-api.monta.com/reference/get-afir-charge-points](/api/afir-charge-points#retrieve-a-list-of-afir-charge-points)

* This endpoint is cursor-paginated
* You can optionally filter by `countryId` — to identify the `countryId`, use this endpoint [https://docs.partner-api.monta.com/reference/getcountries](/api/countries#retrieve-a-countries)

### ⏱️ Rate Limiting

To ensure fair usage and stability, the following rate limit applies:

* 100 requests per 10 minutes

:::note

Clients exceeding the limit will receive a `429 Too Many Requests` response. If you need higher limits, please contact Monta support.

:::