Methodology
Commercial Products
Commercial User GuideHobbyist and Research Products
Help & Support
Potential Solcast errors that can occur when making API requests
Check the FAQs to troubleshoot any common issues with interpreting and using data in the Solcast API or Tookit.
400 Errors
If you receive a 400 Bad Request response alongside the response error code “Unsupported output_parameter(s) requested”, this is likely because the output parameters you are trying to send within the API is not available on the plan you are on.
This could include, but is not limited to, requesting a period that is not applicable to your plan. Such as requesting PT15 when only PT30 or PT60 is available.
Another possible error code you may receive is “Predicate” which likely indicates that one or more parameters you have sent through are incorrectly spelled. In this instance, double check with the account subscriptions page to ensure that the values match the Solcast spelling.
If however you are making the API request to our unmetered locations, these locations will allow you to query all the available parameters, so you can evaluate the usefulness of the responding value for your own purposes.
In most instances the error reponse will also let you know which of the output parameters are causing the 400 error, however, please also check our API Docs, to ensure that the parameters are indeed available for that endpoint.
401 Errors
If you are receiving the error code: “This account has been locked”, it is likely that your account has been locked. This is primarily due to too many incorrect password attempts in the Solcast toolkit account login. If this is the case, please complete a password reset, and once successful, this will unlock your toolkit account and enable you to start making API requests again.
You may also receive this error if you are not authenticated to receive data from this specific endpoint. The error will display “This site can’t be reached” or “ERR_INVALID_RESPONSE”. If you are using the web browser to obtain the data, you can log into the Solcast toolkit and then visit the endpoint again, or alternatively (especially if you’re making the call from a server or third party tool) is to include the “&api_key={insert_your_api_key_here}” at the end of your URL and that should authenticate you to receive the data.
402 Errors
Typical error messages are 402 Forbidden or 402 Payment Required.
This is likely caused by going over your quota of requests. In order to check, within the Solcast toolkit, select your user details at the top right, then within the dropdown, select Manage Subscriptions. Here you will be able to see your requests limit, and know if you have exceeded that value.
As per the screenshot above, you can also select view logs, or View request log (or View request log by location)
This will call our Service Stack tool to provide the specific API calls for this API endpoint, where it may provide further detail for troubleshooting.
403 Errors
If you are seeing 'Forbidden' on my API requests.
404 Errors
There are many possible situations where you receive 404 errors.
One of the potential reason could be the API key being entered incorrectly. In this case, the response status message will be ApiKey does not exist.
429 Errors
If you are encountering 429 errors, we advise that you may be trying to send through too many requests from a single server at a given time. Please try waiting, or creating larger gaps between calls to alleviate this error.
To view your rate limit, please click on your name (top right), then Manage Subscription, then within your product plan, you should be able to view the Rate Limit.
Each product will have it’s own rate limit. Please ensure that you double check this prior to coding.