Solis API Troubleshooting

Sample1: Error is reported as "wrong sign".

Response example:

{"timestamp": 1718110031698,"status": 403,'error": "Forbidden",'message": "wrong sign",'path":"/v1/api/userstationList'}

Troubleshooting:

1. Confirm that the correct interface name is v1/app/userStationList.

2. 'message': 'wrong sign' means that the authorization signature is incorrect.

Authorization : "API " + apiId + ":" + Sign

Sign  =  base64(HmacSHA1(apiSecret,POST+ "\n"

+ Content-MD5 + "\n" 

+ Content-Type + "\n" 

+ Date + "\n" 

+ CanonicalizedResource))

You can refer to the Hash and KBC calculator¹ for signature calculation.

e.g.:

Reference 1:https://dinochiesa.github.io/hmachash/index.html

Sample 2: Error is reported as "data is null".

Response example:

 {
"success": true,
"code": "1",
"msg": "Communication error. Please refresh and try again later",
"data": null
} 

Troubleshooting:

Check if "Body" content meets our API request requirement, following the code example in guidance. If you're not able to find the error in passing parameter, provide the details of API name and Body for us to check. If possible, you can ask API key for us to test and check.

Sample 3: Date parameter related passing error.

Error message example 1:

{"timestamp":1722499310580,"status":403,"error":"Forbidden","message":"Date can not be empty","path":"/v1/api/inverterDetail"}

Error message example 2:

{"timestamp" : 1723449164252,"status": 408,"error": "Request Timeout","message": "request time out","path": "/v1/api/inverterDetail"}

Troubleshooting:

Check Date parameter comparing to code example. Note that the GMT time cannot be earlier or later than the current time by 15 minutes, otherwise the API call will fail.