# Error Handling ## Error Handling Requests with application or business logic errors will return with an HTTP code of 200, but with additional fields for error code and message. For example: ```json { "code": 171008, "message": "Internal Server Error" } { "code": 171018, "message": "expire time exceeds global limit 120s" } ``` To verify the response status, please check `success` bool, or if `code` is present in the response. {% hint style="info" %} Please note that for endpoints that typically return an array, when they encounter an error, the response will be in object format. {% endhint %} ## Error Codes The list of most common error codes returned by CrossChain Swap APIs. For other unknown errors, please reach out to Native team members via existing channel.
CodeMessageReasonMitigation
351015requested amount smaller than token out minimum wei [xxx]The buying (bridge to) token amount is too small. Check minimum-bridge-to-amount for the minimum amount and avoid bridging orders that are too small.
131003failed to parse parametersIssues with input parameters. Usually due to incorrect formats.Check input format. Avoid passing floats in unsupported params like amount_wei or timeout_millis
131004invalid parameterIssues with input parameters. Usually due to input conflicts or missing params.Check the related API reference to see if any param is duplicated or missing.
201001auth get api key is invalidAuth error.Use correct api key.
201005rate reach limitRate limit is hit.Reduce traffic.