PPC Cloud Gateway — Route Simulator

caller identity & scope (set these first)

In production api-4 forwards these from the verified login token; here you set them by hand. The routes are scoped by them: with GATEWAY_ENFORCE_SCOPE on, /v1/plants and the inverter lists return only what the Client-Id (company) is allowed to see, so an empty list usually means the company id is missing or wrong. Changing any field below reloads the plant list.

Client-Id (company; required when GATEWAY_ENFORCE_SCOPE is on) Client-Hash (scopes visible plants; legacy API-3) X-Allowed-Assets (comma-separated legacy asset ids; blank = unrestricted) Acting user email (X-Delfos-User-Email) Authorization (Bearer JWT, for signature/exp policy & claim-derived scope) X-Gateway-Token (service auth; required when GATEWAY_UPSTREAM_TOKEN is set)

Operator

Plant / solar field Inverter(s) — pick one, or several for a batch

Command Power limit value (0-100, POWER_LIMIT only) Reason Use the plant's stored otp_secret (lab — gateway computes the code) OTP (your 6-digit 2FA code)

Local logs = the plant's command_logs (proxied). Gateway audit = this gateway's own ledger of every attempt, incl. refused.

Response

Pick a plant to load its inverters.