🚧

API keys must be whitelisted to use this endpoint. Please contact us at [email protected] if you'd like to do so

There are three options for passing spam reports (see below). The event_type passed can be one of one of user_hid, user_unhid, user_burned, mark_as_spam, mark_as_not_spam or omitted.

  1. Spam report for an individual NFT - send a POST request with contract_address, chain_id, token_id, and event_type, e.g.,

{
"contract_address":"0x04fdc08598f50ffb09ae9a063b04c1227a546d7e",
"chain_id":"ethereum",
"token_id":"2",
"event_type":"mark_as_spam"
}

(On Solana, token_id will be ignored).


  1. Spam report for a contract - send a POST request with contract_address, chain_id, and event_type, e.g.,

{
"contract_address":"9sBjS9PBSyRYLgo9WMVWFLCjNTD11eDZKnjyCEpJL55a",
"chain_id":"solana",
"event_type":"mark_as_spam"
}

(On Solana, contract_address is often called mint address).


  1. Spam report for a collection - send a POST request with collection_id, and event_type, e.g.,

{
"collection_id":"6a9fdb2276b6b70d0bd33175f563a61d",
"event_type":"mark_as_spam"
}

In each case, if event_type is blank, the report will be assumed to be mark_as_spam

Language
Click Try It! to start a request and see the response here!