Error code reference
| Code | Meaning | Common message | What to do |
|---|---|---|---|
0 | Success | Ok | Read the returned data from info. |
400 | Invalid parameters | missing params ... | Check the required parameters, parameter names, and value formats. |
401 | Authentication failed | authentication error | Check your client-id and access-key. |
402 | Insufficient balance | Insufficient account balance(renewal) | Add funds or reduce the scope of the renewal before trying again. |
403 | Renewal not supported | does not support renewal | Check the node’s status and renewal eligibility. |
404 | Order not found | order does not exist | Check that trade_no is correct and belongs to the current account. |
422 | Business validation failed | Renewal period or renewal error | Check the renewal period, node status, and applicable product rules. |
429 | Too many requests | request error | Reduce your request rate and try again later. |
500 | Service error | request error | Try again later. Contact Support if the error continues. |
400: Invalid parameters
Check the following:
- All required parameters are present.
- Parameter names use the correct spelling and letter case.
- Multiple node IDs are separated with standard commas.
page_no,page_limit, andrenew_dayscontain valid integers.page_limitdoes not exceed the maximum value of100.
If the node parameter is missing from a renewal request, the message may say missing params node_ids. The correct request parameter name is node_id.
401: Authentication failed
Make sure that:
- Both
client-idandaccess-keyare present in the request headers. - Neither credential contains extra spaces, line breaks, or quotation marks.
- The
client-idandaccess-keybelong to the same account or integration environment. - The credentials are still valid.
402: Insufficient balance
This error normally occurs when renewing nodes. Confirm that your available account balance can cover the full renewal amount before submitting the request again.
403: Renewal not supported
One or more nodes are not currently eligible for renewal. Check the node status, product type, and expiration time. If the reason is unclear, contact QuarkIP Support and provide the affected node IDs.
404: Order not found
Make sure trade_no is complete, belongs to the current account, and was requested through the correct API domain.
422: Business validation failed
This response means that the request format was accepted, but the renewal period, node status, or another business condition did not pass validation. Check msg for additional context.
429: Too many requests
Reduce your request rate and retry after a delay. For automated integrations, use a backoff strategy that gradually increases the delay between attempts. Do not retry continuously without waiting.
500: Service error
Try the request again later. Automated integrations may retry occasional 500 errors a limited number of times. If the error continues, contact QuarkIP Support.
What to include when contacting Support
To help the Support team investigate the issue, provide:
- The request time and time zone
- The endpoint path and HTTP method
- The HTTP status, response
code, andmsg - Any relevant order IDs or node IDs
- The request parameters needed to reproduce the issue, with sensitive values removed
Never send your complete API token or proxy password.
