CLEAR SOURCES.
USEFUL CONTEXT.

What we publish

ChargeAPI.com publishes educational guides about EV charging APIs, vehicle integrations, battery data, and charging standards. The material helps readers reason about an integration and find an appropriate official starting point. It is organized around distinct topics so a reader can move from a broad introduction to a focused technical question.

Sources and factual claims

We favor documentation from the organization responsible for an API, standard, or dataset. Each Charge Journal article includes a primary editorial reference that supports its subject. Official documentation is the authority for a provider’s current access requirements, supported behavior, and usage conditions.

Examples and practical recommendations add interpretation around those references. We distinguish provider-specific facts from general engineering reasoning, and avoid making claims about service coverage, price, or performance without evidence.

Examples and illustrations

JSON records, scenarios, calculations, and illustrations are educational examples unless explicitly identified otherwise. Example values are not live observations. A simplified calculation explains a relationship; it should not be treated as a promised charging outcome or a complete provider contract.

Independence and scope

ChargeAPI.com is an independent resource. References to manufacturers, protocols, and organizations identify the relevant subjects and sources; they do not imply a partnership, certification, or endorsement. The site does not issue production API keys or provide a charging control service.

Reading dates in context

Publication dates identify individual articles in the archive. When you implement an integration, verify current provider documentation even if a guide’s explanation remains useful. API access rules, available fields, and implementation details can evolve separately from the general concepts discussed in an article.

Corrections and feedback

If you find an error or an official reference has changed, email [email protected]. Include the page address, the relevant passage, and a primary reference where possible. Clear, specific feedback makes it easier to assess the issue and improve the explanation.