{
  "opencollection": "1.0.0",
  "info": {
    "name": "IPGeolocation.io: Abuse Contact ASN Lookup IP Abuse Contact API",
    "version": "3.0"
  },
  "request": {
    "auth": {
      "type": "apikey",
      "key": "apiKey",
      "value": "{{apiKey}}",
      "placement": "query"
    }
  },
  "items": [
    {
      "info": {
        "name": "IP Abuse Contact",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "IPGeolocation.io IP Abuse Contact Lookup",
            "type": "http"
          },
          "http": {
            "method": "GET",
            "url": "https://api.ipgeolocation.io/v3/abuse",
            "params": [
              {
                "name": "ip",
                "value": "",
                "type": "query",
                "description": "An IPv4 address or IPv6 address to look up. When omitted, the API\nresolves the public IP of the requesting client. Empty or whitespace-only values\nare treated the same as omission and resolve caller IP. Pass `ip` only once. If multiple `ip` query parameters are sent,\nvalues may be merged and treated as invalid input (HTTP 400).\n"
              },
              {
                "name": "fields",
                "value": "",
                "type": "query",
                "description": "Comma-separated list of fields or objects to return. Everything else is omitted.\nThe `ip` field is always returned regardless of this filter.\n\nSupports dot-notation for nested fields: `abuse.route`, `abuse.organization`.\n\nIf the same field or object is specified in both `fields` and `excludes`, the\nobject is still returned, but it will be empty.\n\nIf you list both an object key and one of its nested fields separated by comma\n(e.g. `abuse,abuse.name`), the full object is returned.\n\nUnknown field paths are ignored. The API still returns HTTP 200.\n\nAvailable on all plans including Free.\n"
              },
              {
                "name": "excludes",
                "value": "",
                "type": "query",
                "description": "Comma-separated list of fields or objects to remove from the response. The `ip`\nfield cannot be excluded.\n\nSupports dot-notation for nested fields: `abuse.name`.\n\nIf the same field or object is specified in both `fields` and `excludes`, the\nobject is still returned, but it will be empty.\n\nUnknown fields or object keys in `excludes` are ignored. The API still returns\nHTTP 200.\n\nAvailable on all plans including Free.\n"
              },
              {
                "name": "output",
                "value": "",
                "type": "query",
                "description": "Desired response format. Defaults to `json` if not specified. You can also\ncontrol the format using the `Accept` header (`application/json`,\n`application/xml`, or `text/xml`). If both are provided, the `output` parameter\ntakes precedence.\n\nIf `output` is unknown or unsupported, it is ignored and the response defaults\nto JSON (`application/json`) with HTTP 200.\n"
              }
            ]
          },
          "docs": "Returns abuse contact information for a single IPv4 or IPv6 address.\n\nThe response includes the organization responsible for handling abuse\ncomplaints related to the queried IP address. This typically contains\nthe abuse contact role, organization name, contact emails, phone\nnumbers, and the registered address.\n\nThis endpoint is intended for reporting malicious activities such as\nspam, phishing, DDoS attacks, and other network abuse.\n\nWhen only abuse contact information is required, using this en"
        }
      ]
    }
  ],
  "bundled": true
}