Skip to main content

Welcome to the AltherGo API

AltherGo provides a robust microservices infrastructure for electric mobility (e-mobility) management. Our architecture was designed under strict scalability and resilience standards, interconnecting drivers, hardware (EVSEs), and financial settlement systems in a high-availability event-driven ecosystem.

Certification and Compliance

The hardware communication architecture strictly adheres to the OCPP 1.6-J and OCPP 2.0.1 protocols, ensuring compliance with European standards and global compatibility with multiple charging station manufacturers.

Architecture Pillars​

The platform is divided into independent service layers to ensure stability and data isolation:

  1. Protocol Gateway (OCPP): Manages persistent WebSocket connections and uses an MQTT message bus to route telemetry and technical commands in real-time.
  2. Financial Engine: Orchestrates payments, digital wallets (Wallets), and integrations with the Pagar.me V5 gateway in an isolated and secure environment.
  3. Event-Driven Workers: Asynchronous processing via BullMQ to ensure the integrity of refunds, notifications, and database synchronization.
  4. B2B Dashboard: Management interface for operators (CPOs) with consumption analysis and multi-tenant corporate fleet management.

Platform Capabilities​

Through our RESTful endpoints, integrators and partners can:

  • Infrastructure Management: Registration of physical stations, connector mapping, and application of dynamic cost assumptions.
  • Charge Orchestration: Triggering of remote commands, instant consumption telemetry monitoring, and application of Smart Charging profiles.
  • Financial Settlement: Capture of transactions with credit cards or PIX, digital balance management, and automatic application of Cashback rules.
  • User Administration: Granular permission control via tags (Tags) and user groups for fleet management.

Security and Authentication​

Security is the central pillar of our infrastructure. We implement modern standards to ensure the integrity of monetary transactions and sensitive hardware data.

Authentication and Scope

Most mutable routes require a valid JWT token sent in the request header. The system guarantees strict data isolation per company (Company Isolation): Authorization: Bearer <jwt_token>

Documentation Structure​

Use the sidebar menu to explore the service domains. We recommend starting with the Infrastructure section to understand the connectivity with the chargers, or the Financial Settlement section to configure the payment flows of your network.