Reference · built on requestConnectorEnergy, EV & distributed resources

Monta Public API

Charge points, charges, EVSE status, and wallet transactions from the Monta charging platform through its Public API.

Request accessPricing ↗

About

Monta runs a charging platform for charge point owners, operators, and drivers. Its Public API at public-api.monta.com lists your charge points with state, connectors, maxKw, lastMeterReadingKwh, and firmware; returns charges with consumedKwh, cost, price, and stopReason; reports an EVSE's availability status and ad-hoc price; and exposes wallet transactions for a team. Charge points connected to Monta over OCPP also return a kWh consumption breakdown per charge. Applications are registered in the Monta portal and granted scopes such as charge-points, charge-transactions, control-charging, and wallet-transactions.

An operator on Fibric reads charges and charge point state and proposes a start, a stop, or a wallet review for your approval.

This is a reference listing. It documents what Fibric would read from Monta Public API and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Charge points through GET /api/v1/charge-points: serialNumber, visibility (public or private), maxKw, type (AC or DC), state, connectors, cablePluggedIn, lastMeterReadingKwh, firmwareVersion
  • Charges through GET /api/v1/charges, filtered by chargePointId, state, fromDate, and toDate, with consumedKwh, cost, price, averagePricePerKwh, stopReason, failureReason, and soc
  • Charge states reserved, starting, charging, stopping, paused, scheduled, stopped, and completed
  • A per-charge kWh consumption breakdown in 3600, 1800, 900, 600, or 300 second buckets for Monta-connected (OCPP) charge points
  • EVSE dynamic status by OCPI EVSE identifier: available, occupied, outOfService, reserved, or unknown, with ad-hoc energyRateUpdate pricing
  • Wallet transactions with state (complete, pending, failed, reserved), fromAmount, toAmount, currency, and exchangeRate, plus the personal team wallet
  • AFIR charge points and UK charge points in OCPI format through the open data endpoints

Proposed actions

  • Target capability: propose starting a charge on a charge point through POST /api/v1/charges with chargePointId (scope control-charging)
  • Target capability: propose stopping a running charge through the stop charge endpoint (scope control-charging)

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Start the overnight charge when the tariff drops

    Read charge points with cablePluggedIn true and no running charge. When the cheap window opens, propose POST /api/v1/charges for each, in order, under the rate limit.

    With Tariff Window

  • Find the charge that stopped early

    Compare consumedKwh, kwhLimit, and stopReason on completed charges against what the vehicle needed. Propose a restart or a note for the driver.

    With Charge Readiness

  • Reconcile the month's charging spend

    Pull charges with cost, price, and currency and wallet transactions by state and date, and propose the reconciliation lines for review.

    With Bill Reconcile, Utility Chargeback

  • Watch the depot's charge points

    Poll charge point state and EVSE status. When a point reports outOfService or a charge fails, propose the ticket and a reassignment to another point.

    With Depot Charging

Requirements

  • A Monta account and an application registered at portal2.monta.app/applications with a clientId and clientSecret
  • Scopes granted to the application: charge-points, charge-transactions, control-charging, and wallet-transactions as needed
  • Charge points connected to Monta over OCPP, for the kWh consumption breakdown
Authentication
OAuth 2.0 client credentials: POST /auth/token with clientId and clientSecret returns an access token that expires within 1 hour and a refresh token that lasts about a month; refresh through /auth/refresh and send Authorization: Bearer on every call.

Limits

  • Rate limit of 10 calls per 60 seconds per user across all applications; Monta says the limit may change
  • Collections use offset pagination with page and perPage from 1 to 100, default 10
  • The public reference lists no webhook, site, team, or price group endpoints, so state is read by polling within the rate limit
  • Only charges on charge points connected to Monta over OCPP return the kWh consumption breakdown

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Monta Public API ↗

Questions and answers

Which scopes does the connector need?
charge-points to list charge points, charge-transactions to read charges and the kWh breakdown, control-charging to start or stop a charge, and wallet-transactions for wallet data. GET /auth/me returns the scopes your application holds.
How often can Fibric poll Monta?
Monta's integration notes set 10 calls within 60 seconds per user across all applications, with a warning that the limit may change. Fibric spaces reads accordingly and uses fromDate and toDate filters so each call returns only new charges.
How are tokens handled?
POST /auth/token with clientId and clientSecret returns an access token that expires within 1 hour and a refresh token. Monta asks integrations to use /auth/refresh rather than resend the secret. Fibric stores the refresh token and exchanges it for a new pair; your secret is sent only on first issue.
Ask about Monta Public API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Monta Public API through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy