Solar Potential API
Overview
To use Solar Potential, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/solarpotentialExample
How to call the Solar Potential API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/solarpotential?lat=37.7749&lon=-122.4194" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/solarpotential?lat=37.7749&lon=-122.4194', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/solarpotential?lat=37.7749&lon=-122.4194', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/solarpotential?lat=37.7749&lon=-122.4194", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"coordinates": {
"latitude": 37.7749,
"longitude": -122.4194
},
"usableHours": {
"avgDailyUsableSunlightHours": 12.19,
"yearlyUsableSunlightHoursRaw": 4448,
"adjustedYearlyUsableSunlightHours": 1557
},
"bestDirection": "South",
"cloudFactor": 0.35,
"disclaimer": "This is a rough estimate based on coordinates and general climate patterns. For precise solar potential, consider local weather patterns, obstructions, and professional assessments."
}
}Authentication
The Solar Potential API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Solar Potential API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Solar Potential API:
Get Solar Potential Data
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
lat | number | required | The latitude of the location Range: -90 - 90 | - | |
lon | number | required | The longitude of the location Range: -180 - 180 | - |
Response
The Solar Potential API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<coordinates>
<latitude>37.7749</latitude>
<longitude>-122.4194</longitude>
</coordinates>
<usableHours>
<avgDailyUsableSunlightHours>12.19</avgDailyUsableSunlightHours>
<yearlyUsableSunlightHoursRaw>4448</yearlyUsableSunlightHoursRaw>
<adjustedYearlyUsableSunlightHours>1557</adjustedYearlyUsableSunlightHours>
</usableHours>
<bestDirection>South</bestDirection>
<cloudFactor>0.35</cloudFactor>
<disclaimer>This is a rough estimate based on coordinates and general climate patterns. For precise solar potential, consider local weather patterns, obstructions, and professional assessments.</disclaimer>
</data>
</response>
status: ok
error: null
data:
coordinates:
latitude: 37.7749
longitude: -122.4194
usableHours:
avgDailyUsableSunlightHours: 12.19
yearlyUsableSunlightHoursRaw: 4448
adjustedYearlyUsableSunlightHours: 1557
bestDirection: South
cloudFactor: 0.35
disclaimer: >-
This is a rough estimate based on coordinates and general climate patterns.
For precise solar potential, consider local weather patterns, obstructions,
and professional assessments.
| key | value |
|---|---|
| coordinates | {latitude:37.7749,longitude:-122.4194} |
| usableHours | {avgDailyUsableSunlightHours:12.19,yearlyUsableSunlightHoursRaw:4448,adjustedYearlyUsableSunlightHours:1557} |
| bestDirection | South |
| cloudFactor | 0.35 |
| disclaimer | This is a rough estimate based on coordinates and general climate patterns. For precise solar potential, consider local weather patterns, obstructions, and professional assessments. |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
coordinates | object | - | |
â”” latitude | number | Latitude coordinate of the location analyzed | |
â”” longitude | number | Longitude coordinate of the location analyzed | |
usableHours | object | - | |
â”” avgDailyUsableSunlightHours | number | Average daily usable sunlight hours for the location | |
â”” yearlyUsableSunlightHoursRawPremium | number | Total yearly usable sunlight hours without adjustments | |
â”” adjustedYearlyUsableSunlightHoursPremium | number | Adjusted yearly usable sunlight hours accounting for clouds | |
bestDirection | string | Optimal solar panel direction (e.g., South, Southwest) | |
cloudFactorPremium | number | Cloud cover factor between 0 and 1 reducing solar potential | |
disclaimer | string | Important disclaimer about estimate accuracy and limitations |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Solar Potential through GraphQL to combine it with other API calls in a single request. Query only the solar potential data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
solarpotential(
input: {
lat: 37.7749
lon: -122.4194
}
) {
coordinates {
latitude
longitude
}
usableHours {
avgDailyUsableSunlightHours
yearlyUsableSunlightHoursRaw
adjustedYearlyUsableSunlightHours
}
bestDirection
cloudFactor
disclaimer
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Solar Potential API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Solar Potential requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Solar Potential API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Solar Potential
Official Solar Potential packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Solar Potential works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Solar Potential?
How many credits does Solar Potential cost?
Each successful Solar Potential API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful solar potential lookups.
Can I use Solar Potential in production?
The free plan is for testing and development only. For production use of Solar Potential, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Solar Potential from a browser?
What happens if I exceed my Solar Potential credit limit?
When you reach your monthly credit limit, Solar Potential API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








