Understanding Supply Update Request Rejection Reasons – CoinGecko

This article aims to clarify the reasons behind your request's rejection and provide insights into how to enhance the chances of approval in future requests.

Rejection Reason	Explanation
Insufficient Information/ Missing Locked Wallets	If your request was declined for this reason, it may be due to insufficient information provided, hindering our team's ability to complete the evaluation and update process. Please review the following items before submitting again: All latest supply information is verified with accurate data provided (e.g. wallet addresses, wallet balances, locked supply, API endpoints) Tokenomics data (contained in the form) is updated to present up-to-date information to all users Verified and accurate API endpoint is provided to prevent malicious actors from gaming the ranking system
Not meeting the required criteria	If you request was declined for this reason, it may to due to the project does not meet our liquidity/quality criteria which may include one or all of the following: Active trading volume over a period of time Orderbook Depth Trading ticker quality Number of exchanges traded on Distribution of tokens Project is encouraged to resubmit once overall liquidity improves.
Incorrect REST API endpoint schema format	All endpoints must adhere to the requirements outlined in this article. Should they not meet these specifications, our team cannot proceed with the update. Please ensure compliance before resubmitting.
Already Updated	The changes you requested have already been implemented. Please visit the relevant coin page to verify them.
Wrong token page was selected	Please select the correct token page when submitting your supply update request as wrong token page will lead to rejection.

Related articles