Error Codes
Most errors from the NFTPort API include an error code: a machine-readable code with a brief explanation.
Below is a list of possible error codes, along with additional information about how to resolve them.
To debug the API calls you have made recently, you can see a log of API calls you have made in the dashboard.
Status code | Error code | Explanation |
---|---|---|
Access | ||
401 | authorization_missing | Your request is missing an API key. Add your API key to the Authorization: header. You can find your API key in the dashboard. |
401 | invalid_api_key | You're using an incorrectly formatted API key. Make sure the key is formatted as a valid UUID. |
403 | invalid_credentials | The API key you're using does not correspond to any NFTPort account. Check if you're using the correct API key. You can find your API key in the dashboard. |
403 | account_suspended | Your API key is valid but your account is suspended. Please reach out to NFTPort support for more information. |
Request validation | ||
422 | invalid_address | You provided an invalid address. Check that the wallet and contract addresses you're sending are valid EVM addresses. |
422 | chain_not_supported | This chain is not supported for this endpoint. Check which features are support for each chain. |
422 | invalid_date | You provided an invalid date. Check that you're providing valid ISO-formatted date. |
422 | invalid_continuation_string | You provided an invalid continuation string. Make sure you're using the correct continuation string you received from a previous request. |
422 | page_number_not_supported | Paging by page number is not supported for this endpoint. Switch to using continuation strings. |
422 | value_error | You provided an invalid value. See error message for details. |
422 | invalid_enumeration | You provided an invalid choice for a parameter. See error message for list of allowed values. |
422 | parameter_missing | The request is missing a required parameter. See error message for details and please make sure the parameter is present. |
422 | invalid_type | You provided a value of invalid type. See error message for details. |
422 | invalid_url | You provided an invalid URL. Make sure the input you provided is a valid URL. |
422 | invalid_file_type | The input file type you provided is not supported. See error message for supported file types. |
422 | invalid_attribute_value | You provided an invalid NFT metadata attribute value. See error message for details. |
422 | invalid_token_id | You provided an invalid token ID. See error message for details. |
422 | invalid_token_quantity | You provided an invalid token quantity. Make sure the token quantity is a positive integer. |
422 | invalid_transaction_hash | You provided an invalid transaction hash. Check that you're providing a correctly formatted transaction hash. |
422 | request_too_large | The request contains too much data to write onto the blockchain in one request. Please reduce the number of tokens in your request. |
Hitting account limits and quotas | ||
403 | mint_limit_exceeded | You've reached the maximum number of NFTs possible to mint on your account (in this billing period). Please see Quotas or check your usage in the dashboard. |
403 | contract_limit_exceeded | You've reached the maximum number of contracts possible to deploy on your account (in this billing period). Please see Quotas or check your usage in the dashboard. |
403 | transaction_limit_exceeded | You've reached the maximum number of transactions possible to make on your account (in this billing period). Please see Quotas or check your usage in the dashboard. |
429 | too_many_requests | Too many requests hit the API too quickly. Make your requests at a lower rate. See Rate limits. |
Other client errors | ||
400 | invalid_request | The request you made was invalid. Please see error message for a description of the problem. |
400 | contract_not_supported | The contract does not support the action you requested. Check which actions are disabled on your contract, deploy a new contract, or reach out to NFTPort support. |
400 | failed_to_fetch_file | We failed to fetch the URL you supplied. Please make sure the URL is correct and a file is available at this URL. |
400 | too_many_files | You attempted to upload more files in a single request than the endpoint allows. Please reduce the number of files in your request. |
400 | transaction_failed | The transaction (e.g. contract deployment) failed. Please retry the transaction. |
403 | forbidden | This action is forbidden on this resource. Please see error message for details. |
404 | not_found | The requested resource was not found. Make sure your request parameters are correct. |
404 | transaction_pending | The transaction is not yet recorded on chain. Please check again in a few seconds. |
405 | method_not_allowed | You attempted to use a HTTP method the endpoint doesn't support (e.g. made a GET request to a POST-only endpoint). Make sure you're using the correct method. |
Server errors (see NFTPort status) | ||
500 | internal_server_error | An unexpected error occurred when processing your request. Please reach out to NFTPort support. |
502 | bad_gateway | An external service returned an error, causing your request to fail. Please reach out to NFTPort support. |
503 | too_many_pending_transactions | Due to high load, there are too many on-chain transactions queued. Please try again shortly or reach out to NFTPort support. |
503 | gas_price_too_high | Due to high gas fees on the network, your request was rejected. Please try again when gas fees are lower or reach out to NFTPort support. |
Updated almost 2 years ago