Authorizing charge Requests

Before charging, vehicles must be authorized. There are three authorization providers:

Internal Authorization: Default option for anonymous charge sessions. Can be configured to require authentication (RFID or Zaptec app).
Web Hooks: Allows 3rd-party authorization using configured HTTP POST requests.
OCPP-J 1.6 Core: Integrates with OCPP-enabled cloud solutions.

Web Hook Authorization

Web hooks enable external systems to authorize charge sessions. Two web hooks are configurable:

Session Start: Called before a session begins.
Session End: Called after a session ends, providing session details.

Configuration

Authentication URL: Configures OAuth token service.
Session Start/End URLs: Specifies the endpoints for session start and end events.

More information on Webhook Authorization can be found here: Webhook authentication

Independent of the authorization method selected for your installation, the following sequence describes communication between vehicle, charging station, ZapCloud and authorization provider