> For the complete documentation index, see [llms.txt](https://i4trust.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://i4trust.ishare.eu/open-call-1/solar-charge-api.md).

# Solar Charge API

Data exchange to implement smart charging incentives is hampered by discrepancies in data formats among different stakeholders. The charging station management applications struggle to request and receive standardised data from Solar Energy producers or rooftop solar asset managers. This creates the challenge of Data Interoperability in EV Charging. Another significant challenge lies in the proprietary nature of real-time data on solar energy production and historical energy demand at charging stations, which is inaccessible to the public. 

Solar Charge API addresses these challenges by designing and deploying a data space for e-mobility and energy stakeholders. The consortium receives data from multiple sources, structures it, and enables other stakeholders to access the data for the regions of interest. The Solar Charge API, supported by [i4Trust Building Blocks](https://github.com/i4Trust/building-blocks), allows participants to exchange structured data under defined rules. i4Trust leverages the [iSHARE Trust Framework](https://framework.ishare.eu/) and its defined authorisation tools to ensure fair data exchange between participants. The user navigates to the SolarCharge API Marketplace to select the Identity provider (IdP) of their organisation. The IdP validates the SolarCharge API as a valid iSHARE Party and prompts the user to grant access to the Marketplace. 

Upon successful authentication, the user can subscribe to the data offering of their choice. Once a data offer is selected and paid for via the FIWARE Marketplace, an Authorization policy is created that specifies the user resource access and permissions. This ensures secure, interoperable, and remunerative data exchange in the e-mobility and energy sectors.

Learn more about the Solar Charge API in the Impact Story.

{% file src="/files/fgS9GwykijmXDAxYnk6J" %}

#### Contributors:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><img src="/files/T6d6Q3Z5Q2BL6OVtSghd" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/f2k2VrdDeRwyzvOT7txd" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/cNMrWk8eQbLuCS1RfLso" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/2lN0dr3SyEwRqDPAbKqD" alt="" data-size="original"></td><td></td><td></td></tr><tr><td><img src="/files/nTYmhAD2PUPPpwFnVgdc" alt="" data-size="original"></td><td></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://i4trust.ishare.eu/open-call-1/solar-charge-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.