1. Error Type

· Connection layer: APIs connect to the connection layer using HTTP. The HTTP STATUS parameter indicates the state of the connection layer.

· Platform layer: If NSP_STATUS exists in the HTTP response header and is not set to 0, the error is captured by the open platform.

· Service layer: Each app determines whether there is an error in the return results and defines the error for each API. Calling parties need to handle the errors by themselves.

Among the error types, errors from the service layer can be captured by the platform and converted to the NSP_STATUS values.

2. Troubleshooting

Handle the errors during service calls based on the following suggestions:

Error Code	Handling Suggestion
0	Check whether the value of HTTP STATUS is normal.
1	Check whether the value of NSP_STATUS is normal.
2	Check whether there is any error in the return values based on the service call description.

3. HTTP STATUS

Result Code	Description
200	Success.
401	Authentication required.
500	Exception in the OpenGW.
502~504	Other network errors.

4. NSP STATUS

Result Code	Description
0	Success.
1	Unknown error.
2	Services are unavailable for now.
3	Unknown method.
4	The number of requested apps has reached the maximum.
5	Requests from unauthorized IP addresses.
6	The session key of the current user has expired.
7	The number of calls exceeded the maximum.
8	API call too frequent.
100	Unknown invalid parameter.
101	Invalid API-KEY.
102	Invalid SESSION-KEY.
103	The value must be submitted in POST mode.
104	Invalid signature.
105	System parameters such as nsp_svc, nsp_ts, and nsp_key not found.
106	The app or session does not have the permission to call the current service.
107	The values of client_id and client_secret need to be re-obtained due to reasons such as algorithm upgrade.
108	The routing fails, and the service delivery address cannot be identified.
109	The nsp_ts value difference goes beyond the allowed range.
110	Internal API exception.
403	No permission.