HomeGuidesAPI ReferenceChangelog
Terms of Use
Changelog
Terms of Use
Back to All

3.263.0 release notes

35 minutes ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Changed GET /public-api/resources/ocpi-commands/v1.0 to return only inbound OCPI commands. Outbound commands are no longer listed, and requesting one through GET /public-api/resources/ocpi-commands/v1.0/{ocpiCommand} now returns HTTP 404.
    2. Changed POST /public-api/actions/charge-point/v1.0/{chargePoint}/reserve/{evse} to reject reservations on roaming charge points with HTTP 422.
    3. Changed POST /public-api/actions/reservation/v1.0/{reservation}/cancel to return HTTP 406 with success: false when the charge point rejects cancellation, instead of HTTP 202. The reservation remains unchanged; send force: true to cancel regardless of the charge point response.
  2. ✨ New features
    1. Added the experimental POST /public-api/actions/id-tag/v1.0/validate endpoint to diagnose an ID tag by its uid, with optional type, evseId, and roaming checks enabled through allowRoaming and roamingConnections. The response includes a diagnostic summary and own-tag, roaming, and history findings without starting a session or changing charging state; eligibility findings do not guarantee immediate session-start success.
    2. Added the optional connectionPointIdentifier field for identifying a circuit's grid connection point to requests and responses on POST /public-api/resources/circuits/v2.0 and PATCH /public-api/resources/circuits/v2.0/{circuit}, and to responses on GET /public-api/resources/circuits/v2.0 and GET /public-api/resources/circuits/v2.0/{circuit}. The field accepts up to 255 characters; send null when updating to clear it, and circuits without a value omit it from responses.
    3. Added the filter[connectionPointIdentifier] query parameter to GET /public-api/resources/circuits/v2.0 for case-insensitive exact matching against a single grid connection point identifier. Values must be strings of at most 255 characters; invalid values return HTTP 422, and commas are treated as part of the identifier rather than as separators.
    4. Added the cdr.processed webhook notification for each newly processed local or received CDR, including credit CDRs, with the CDR's id, roamingId, isLocal, createdAt, and applicable operator, session, and credit details. It can be selected through POST /public-api/notifications/v2.0, PUT /public-api/notifications/v2.0/{notification}, and POST /public-api/actions/notifications/v1.0/{notification}/resend, and appears in subscription responses on those create/update endpoints and on GET /public-api/notifications/v2.0 and GET /public-api/notifications/v2.0/{notification}.
  3. 🗑️ Deprecations
    1. Deprecated the cdr.received webhook notification in favor of cdr.processed, which covers both local and received CDRs. Existing subscriptions continue to work; when migrating, the old notification's id corresponds to the new notification's roamingId, not its id.