Blink Charging OCPI Roaming Interface

In September 2025 Blink joined Hubject's Intercharge eRoaming platform as a charge point operator (CPO), using the industry-standard Open Charge Point Interface (OCPI) protocol so partner e-mobility service providers (eMSPs) on Hubject's hub can discover Blink stations, authorize charging, and receive standardized OCPI-based billing/CDRs across the US, Canada, and Mexico. This is a B2B roaming interface brokered through Hubject rather than a direct self-serve developer API; Blink does not itself publish a public OCPI base URL, credential process, or version endpoint - integration happens through Hubject's platform-to-platform OCPI handshake.

API entry from apis.yml

apis.yml Raw ↑
aid: blink:blink-ocpi-roaming-interface
name: Blink Charging OCPI Roaming Interface
tags:
- OCPI
- Roaming
- eMSP
- Hubject
- Intercharge
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://blinkcharging.com/news/hubject-teams-with-blink-charging-to-further-expand-intercharge-network-across-north-america
baseURL: https://blinkcharging.com
properties:
- url: https://blinkcharging.com/news/hubject-teams-with-blink-charging-to-further-expand-intercharge-network-across-north-america
  type: PressRelease
- url: https://www.hubject.com/blog-posts/hubject-teams-with-blink-charging-to-further-expand-intercharge-network-across-north-america
  type: Documentation
description: In September 2025 Blink joined Hubject's Intercharge eRoaming platform as a charge point
  operator (CPO), using the industry-standard Open Charge Point Interface (OCPI) protocol so partner e-mobility
  service providers (eMSPs) on Hubject's hub can discover Blink stations, authorize charging, and receive
  standardized OCPI-based billing/CDRs across the US, Canada, and Mexico. This is a B2B roaming interface
  brokered through Hubject rather than a direct self-serve developer API; Blink does not itself publish
  a public OCPI base URL, credential process, or version endpoint - integration happens through Hubject's
  platform-to-platform OCPI handshake.