2025 API LTA release notes

Prev Next

Release date

Released features

28.5.2025

API upgrade

The API service accessible at URLs starting with https://solargis.info/ws/rest/datadelivery/request (Solargis API LTA) has been upgraded to provide enhanced transparency and usability.


New response headers for enhanced transparency:

Custom response headers are now included in every API response (where applicable) to provide real-time visibility into API usage and limits:

  • solargis-usage-total and solargis-limit-total: Show the total number of calls made and the allowed limit for the entire subscription period.

  • solargis-usage-unique-locations and solargis-limit-unique-locations: Monitor the number of unique locations accessed, valid for the entire subscription period.

  • solargis-request-id: Assigns a unique ID to every API transaction for easier tracking and support.

Users can now check their API consumption after each call for improved transparency and self-management.


Usage API discontinued:

The Usage API previously available at https://solargis.info/ws/usage/ has been discontinued.

  • Usage information is now provided directly in each HTTP response header.


New HTTP response codes:

API error handling has been improved with updated response codes:

  • 429 Too Many Requests is now returned when rate limits are exceeded (previously 403 Forbidden).

  • 401 Unauthorized is now returned for invalid API keys or tokens (previously 403 Forbidden).


More helpful error messages:

Error messages have been improved for greater clarity and easier troubleshooting.


Demo access updates:

  • The demo access password for the pvplanner endpoint (Solargis API LTA) is now 'demo_pvplanner'.

  • The password for the demo subscription to the datadelivery endpoint (Monitor API, Forecast API) remains 'demo'.


Cleanup of Solargis API LTA response:

The LTA API response now includes only those properties from the PV system element that directly affect simulation results.

  • Irrelevant properties have been removed from the XML response for greater clarity and efficiency.


Untouched API interface and data format:

This upgrade does not change the API interface or data format (XML).

  • Data values remain unchanged, ensuring compatibility with existing integrations.