Capability area

Integrations and API

Build on Flowion through its documented, versioned REST API.

Build on the Flowion REST API

A documented, versioned REST API for your chargers, sessions and commands, with API keys scoped to one project or the whole organization, in live or sandbox mode.

Everything the console does goes through the same API that you can call from your own code. Every route lives under /v1, and you can try any endpoint from its page in the API reference with a Try it button, signed in or with an API key.

Your own systems use an API key. You choose its mode (live for real chargers, sandbox for test data and virtual chargers only), its reach (one project, or every project in the organization) and an optional expiry. A key can never hold the Owner policy, and revoking a key takes effect on the next request. People use their sign-in, which the API checks with a proof tied to a key their browser holds.

Within /v1, changes only add: new fields, endpoints, error codes and enum values. Something that is going away is deprecated first and stays for at least six months, announced in the reference, in the API document and in Deprecation and Sunset headers on every response. Lists page with a nextCursor, and commands to chargers go through one endpoint that queues while a charger is offline and can be retried safely with an Idempotency-Key.

Good to know

  • Read responses tolerantly: a new field, error code, enum value or union variant can appear within /v1 without notice.
  • Every route under /v1 shares one request budget per IP address; every response shows where you stand, and the budget is described, with no figure, in the rate limits guide.
  • An API key can never hold the Owner policy, and holds exactly one policy binding.
  • A sandbox key reaches only sandbox data and a live key only live data.