Skip to main content
A network holds everything EVPanda records about one of your systems: its traffic, its discovered entities, its issues, and its API keys. The two are separate. Different entities, different rule sets, different API keys. A service that speaks both protocols needs one network of each and one SDK client of each. Create one network per system, per environment. Chargers, platforms, and tenants are discovered from traffic; you never register them by hand.

​
Network settings

Under the network’s Settings tab.
​
boolean
default:"false"
Reports fields the protocol does not define. Useful for conformance testing, noisy if your fleet uses vendor extensions.
​
boolean
default:"true"
Enables the behavioral checks that flag traffic which breaks no protocol rule but signals a real problem.
​
integer
default:"30"
Charger networks only. Seconds to wait for a CALLRESULT before an OCPP call counts as unanswered. Range 1 to 600.
​
integer
default:"300"
Charger networks only. Seconds of silence after which a charger reads as offline. Range 30 to 900. Set it to at least twice your heartbeat interval.
Roaming networks also carry the OCPI version and your OCPI role (CPO, EMSP, or HUB), which the validation engine uses to decide which side of an exchange is expected to do what.

​
API keys

A key authorizes one SDK client to write into exactly one network.
1

Generate

Open the network’s Settings tab and generate a key. The raw value, evp_sk_..., is shown once. EVPanda stores only a hash of it.
2

Store

Put it in your secret manager and expose it as EVPANDA_API_KEY. Every SDK reads that variable when no key is passed in code.
3

Rotate

Generate the new key, deploy it, confirm traffic still arrives, then revoke the old one. Revocation is immediate.
Keys are scoped and write-only. An OCPP key cannot write OCPI traffic or reach another network, and no ingestion key can read messages, issues, or settings.
A revoked or wrong-protocol key returns 401. The SDK treats that as permanent and does not retry, so nothing arrives and nothing is buffered forever. Check droppedUndeliverable after a rotation.

​
Endpoint

Every SDK defaults endpoint to the production ingestion API:
Set it only to reach another environment. The SDK appends the protocol route itself: POST /v1/ocpp or POST /v1/ocpi.

​
Next

Identity

Attributing a message to a charger or partner.

Data flow

Event shapes, redaction, and limits.