What authentication does the Powerly API use?

The Powerly API uses a client credentials flow via POST /auth/token. Provide grant_type, client_id, and client_secret in the request body to receive a time-limited access_token. Through Jentic, these credentials are stored encrypted and token acquisition is handled automatically.

Can I paginate through all charging resources with the Powerly API?

Yes. The GET /resources endpoint accepts limit and offset query parameters. The response includes a total field indicating the full resource count, enabling you to paginate through all available charging stations by incrementing the offset in subsequent requests.

What are the rate limits for the Powerly API?

Specific rate limits are not documented in the spec. Access tokens obtained from POST /auth/token have an expires_in field indicating their validity period. Implement token caching and refresh logic to minimize authentication requests.

How do I list EV charging stations through the Powerly API using Jentic?

Install the SDK with pip install jentic, then search for 'list EV charging stations'. Jentic returns the GET /resources operation schema with optional limit and offset parameters. Jentic handles authentication automatically, so you can execute directly to receive paginated charging resource data.

Can I limit what my agent is allowed to do with the Powerly API?

Yes. Because you run Jentic One yourself, your own rules decide which Powerly operations and credentials the agent may use. This spec exposes only read lookups, so you can allow listing charging resources with GET /resources and fetching a single station with GET /resources/{id} while blocking everything else. You can also pin the agent to one station id in the path, and no write action exists to grant.