A list of all the possible order ERROR_CODE_STRING that you can encounter when creating an order.

Error schema:

{
  "success": false,
  "data": null,
  "message": "Invalid order payload (ERROR_CODE_STRING)."
}

NONCE_EXECUTED_OR_CANCELLED

Cause	Solution
The `nonce` set in the MakerOrder has been cancelled or already executed.	Retrieve the correct nonce from the get order nonce API endpoint.

NONCE_BELOW_MIN_ORDER_NONCE

Cause	Solution
The `nonce` set in the MakerOrder has been cancelled.	Retrieve the correct nonce from the get order nonce API endpoint.

ORDER_AMOUNT_CANNOT_BE_ZERO

Cause	Solution
The `amount` set in the MakerOrder is zero.	For ERC-721 collections, set the amount to 1. For ERC-1155 collections, set the amount to an integer >= 1.

MAKER_SIGNER_IS_NULL_SIGNER

Cause	Solution
The `signer` set in the MakerOrder is the zero address.	Change the signer address to a valid one.

INVALID_S_PARAMETER_EOA

Cause	Solution
The signature is invalid. More precisely, the `s` parameter.	Ensure the signature is a valid EIP-712 signature.

INVALID_V_PARAMETER_EOA

Cause	Solution
The signature is invalid. More precisely, the `v` parameter.	Ensure the signature is a valid EIP-712 signature.

NULL_SIGNER_EOA

Cause	Solution
The `signer` of the MakerOrder is the zero address. cries	Use a different address.

WRONG_SIGNER_EOA

Cause	Solution
The `signer` of the MakerOrder is different from the expected signer.	Ensure the signer address set in the MakerOrder is correct, you are signing the MakerOrder from the correct account, and the signature is a valid EIP-712 signature.

SIGNATURE_INVALID_EIP1271

Cause	Solution
The EIP-1271 signature in the MakerOrder is invalid.	Ensure the signature is a valid EIP-1271 signature.

MISSING_IS_VALID_SIGNATURE_FUNCTION_EIP1271

Cause	Solution
The `signer` set in the MakerOrder is a contract which does not implement the EIP-1271 standard.	Ensure the signer address set in the MakerOrder is correct and implements the EIP-1271 Standard Signature Validation Method for Contracts

CURRENCY_NOT_WHITELISTED

Cause	Solution
The `currency` address set in the MakerOrder is not whitelisted.	The only whitelisted currency is WETH. You can find the address in the LooksRare SDK - Addresses.

STRATEGY_NOT_WHITELISTED

Cause	Solution
The `strategy` address set in the MakerOrder is not whitelisted.	The only whitelisted strategies are `StrategyStandardSaleForFixedPrice` and `StrategyAnyItemFromCollectionForFixedPrice`. You can find the latest addresses in the LooksRare Docs - Deployed Contract Addresses.

MIN_NET_RATIO_ABOVE_PROTOCOL_FEE

Cause	Solution
The `minPercentageToAsk` is invalid because it's too high. The protocol fee will take more than the `minPercentageToAsk` set in the MakerOrder.	Reduce the `minPercentageToAsk` based on the protocol fee. You can find the current protocol fee by calling the `viewProtocolFee` in a strategy contract. For example: StrategyStandardSaleForFixedPriceV1B - viewProtocolFee. The current protocol fee is 150 (1.5%).

MIN_NET_RATIO_ABOVE_ROYALTY_FEE_REGISTRY_AND_PROTOCOL_FEE

Cause	Solution
The `minPercentageToAsk` is invalid because it's too high. The protocol fee + collection rebate will take more than the `minPercentageToAsk` set in the MakerOrder.	Reduce the `minPercentageToAsk` based on the protocol fee. The current collection rebate is 50 (0.5%). Therefore, the `minPercentageToAsk` should be 9800. `10000 - 150 (protocol fee) - 50 (rebate)`

MIN_NET_RATIO_ABOVE_ROYALTY_FEE_ERC2981_AND_PROTOCOL_FEE

Cause	Solution
The `minPercentageToAsk` is invalid because it's too high. The protocol fee + collection rebate will take more than the `minPercentageToAsk` set in the MakerOrder.	Reduce the `minPercentageToAsk` based on the protocol fee. The current collection rebate is 50 (0.5%). Therefore, the `minPercentageToAsk` should be 9800. `10000 - 150 (protocol fee) - 50 (rebate)`

MISSING_ROYALTY_INFO_FUNCTION_ERC2981

Cause	Solution
An issue occurred when calling the `royaltyInfo` function on the collection contract.	Get in touch with us in our Developers Discord for further support.

NO_TRANSFER_MANAGER_AVAILABLE_FOR_COLLECTION

Cause	Solution
The collection is not supported.	Get in touch with us in our Developers Discord for further support.

CUSTOM_TRANSFER_MANAGER

Cause	Solution
The collection is not supported.	Get in touch with us in our Developers Discord for further support.

ERC20_BALANCE_INFERIOR_TO_PRICE

Cause	Solution
Your ERC-20 balance (WETH) is too low to cover the `price` defined in your MakerOrder.	Swap more ETH to WETH to cover the price you set in the MakerOrder object.

ERC20_APPROVAL_INFERIOR_TO_PRICE

Cause	Solution
The allowance you set for the LooksRare Exchange contract is lower than the `price` defined in your MakerOrder.	Increase the allowance by calling the `approve` function on the WETH contract passing the LooksRare Exchange contract address as the operator, and a higher amount in allowance.

ERC721_TOKEN_ID_DOES_NOT_EXIST

Cause	Solution
The `tokenId` set in the MakerOrder does not exist.	Ensure the collection address and tokenId values are correct.

ERC721_TOKEN_ID_NOT_IN_BALANCE

Cause	Solution
You don't own the `tokenId` defined in the MakerOrder.	Ensure the collection address and tokenId values are correct.

ERC721_NO_APPROVAL_FOR_ALL_OR_TOKEN_ID

Cause	Solution
The `TransferManagerERC721` contract is not approved to transfer the `tokenId` specified in the MakerOrder.	Call either `setApprovalForAll` or `approve` on the collection contract and approve the TransferManagerERC721 to transfer the asset. `setApprovalForAll` is recommended to save gas. If you use `approve`, you'd need to approve each individual token before listing it the first time.

ERC1155_BALANCE_OF_DOES_NOT_EXIST

Cause	Solution
An issue occurred when calling the `balanceOf` function on the collection contract.	Get in touch with us in our Developers Discord for further support.

ERC1155_BALANCE_OF_TOKEN_ID_INFERIOR_TO_AMOUNT

Cause	Solution
Your balance does not cover the `amount` for the `tokenId` specified in the MakerOrder.	Ensure the collection address, tokenId and amount set in the MakerOrder are correct.

ERC1155_IS_APPROVED_FOR_ALL_DOES_NOT_EXIST

Cause	Solution
An issue occurred when calling the `isApprovedForAll` function on the collection contract.	Get in touch with us in our Developers Discord for further support.

ERC1155_NO_APPROVAL_FOR_ALL

Cause	Solution
The `TransferManagerERC1155` is not approved for all.	Call the `setApprovalForAll` and approve the TransferManagerERC1155 contract.