API documentation
?? ??? ?? ??
?? the current abuse status of a ??? (complaints, hold lifecycle, scenario classification). ????s a machine-readable summary suitable f?? resellers monit??ing ???s on behalf of their customers.
Content-Type
application-json
????
abuse
??
get_abuse_report
?? ????
| ???? ?? | ?? | ?? | ?? |
|---|---|---|---|
| domain | ??? (3-60) | ??? ?? | example.com |
?? ????
| ???? ?? | ?? | ?? |
|---|---|---|
| domain | ??? | ??? ?? |
| scenario | ?? | Current abuse scenario classification (one of six ???-level states) |
| scenario.status | ??? | ?? phrase. One of: "???rmal", "Under Review", "?? ? ClientHold", "ClientHold", "??d", "??Hold" |
| scenario.impact | ??? | Impact phrase paired with the status, e.g. "?? risk of restriction", "Currently restricted", "??? restriction" |
| scenario.action | ??? | Recommended ??-step phrase f?? the ??? owner |
| hold | ?? | Hold lifecycle timeline |
| hold.state | ??? | Current hold state: none / pending / applied |
| hold.pending_since | ??time | When the ??? entered the pending-hold queue (null when no hold rec??d exists) |
| hold.scheduled_at | ??time | Planned clientHold execution time. ?? the case is not resolved by this time, clientHold will be applied automatically. |
| hold.applied_at | ??time | When clientHold was actually applied. Null while the hold is still pending. |
| complaint | ?? | Aggregated complaint statistics f?? this ??? |
| complaint.case_count | ?? | ?? of distinct abuse cases involving this ??? (open + closed) |
| complaint.earliest_at | ??time | Timestamp of the earliest complaint received f?? this ??? |
| complaint.latest_at | ??time | Timestamp of the most recent complaint received f?? this ??? |
| complaint.categories | ???[] | Distinct abuse categ??ies across all related cases, e.g. ["Phishing", "Malware"] |
| complaint.is_dns_abuse | Boolean | True when at least one case is classified as DNS Abuse |
| complaint.has_evidence | Boolean | True when at least one case has been confirmed to have sufficient evidence |
| complaint.reported_urls | ???[] | URLs extracted from complaint emails f?? this ??? (deduplicated across all related abuse rec??ds). Empty array when the scenario is ???rmal, ??Hold, ?? an ICANN-directed ClientHold. |
| details_url_hint | ??? | English hint guiding the customer to the console path that shows full case details ? the AI-generated complaint summary |
?? ??
{
curl https://api.nicenic.net/v2/?category=abuse&action=get_abuse_report&domain={domain}
-H "Authorization: username:api_secret"
-H "Content-Type: application/json"
}
?? ??
0 OK
?? ??
{
"code": 0,
"msg" : "success",
"data" : {
"domain": "example.com",
"scenario": {
"status": "Pending ClientHold",
"impact": "At risk of restriction",
"action": "Submit supporting materials now"
},
"hold": {
"state": "pending",
"pending_since": "2026-04-20 10:30:00",
"scheduled_at": "2026-04-22 10:30:00",
"applied_at": null
},
"complaint": {
"case_count": 3,
"earliest_at": "2026-03-12 09:14:00",
"latest_at": "2026-04-22 18:02:00",
"categories": ["Phishing", "Malware"],
"is_dns_abuse": true,
"has_evidence": true,
"reported_urls": [
"http://example.com/promo/win-iphone",
"http://example.com/dl/installer.exe"
]
},
"details_url_hint": "For full case details and the AI-generated complaint summary, sign in to www.unionroom.cn and go to My Account > My Products > Domain Name > Health Check."
}
}
400 ??? ??
{
"code": 400,
"msg" : "Request parameter error",
}
