Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Menggunakan Evaluate API
Halaman ini menjelaskan cara menggunakan Evaluate API agar aplikasi klien Anda dapat mengevaluasi potensi bahaya URL. API ini menampilkan skor keyakinan yang menunjukkan potensi bahaya URL berdasarkan daftar yang tidak diizinkan, model machine learning, dan aturan heuristik. Jika Anda menginginkan hasil biner, bukan skor
keyakinan, gunakan Lookup API.
Catatan: URL yang dikirimkan ke Evaluate API dapat menjalani pemrosesan tambahan, termasuk crawl.
Untuk mengevaluasi URL, kirim permintaan HTTP POST ke metode evaluateUri. Pahami pertimbangan berikut saat mengevaluasi URL:
Evaluate API mendukung satu URL per permintaan. Jika Anda ingin memeriksa beberapa
URL, kirim permintaan terpisah untuk setiap URL.
URL harus valid dan tidak perlu dikanonisasi. Untuk mengetahui informasi
selengkapnya, lihat RFC 2396.
Evaluate API mendukung tiga threatType: SOCIAL_ENGINEERING, MALWARE, dan UNWANTED_SOFTWARE.
Tidak digunakan lagi. Kolom allow_scan digunakan untuk menentukan apakah Web Risk diizinkan memindai URL yang diberikan. Fungsi ini tidak dapat dinonaktifkan lagi
di Evaluate API. Lihat API Lookup dan Update untuk opsi bebas crawl.
Respons HTTP POST menampilkan skor keyakinan untuk
threatType yang ditentukan. Skor keyakinan menunjukkan tingkat keyakinan yang menunjukkan
seberapa berisiko URL yang ditentukan.
Permintaan API
Sebelum menggunakan salah satu data permintaan,
lakukan penggantian berikut:
URL: URL yang perlu dievaluasi.
Metode HTTP dan URL:
POST https://webrisk.googleapis.com/v1eap1:evaluateUri?key=API_KEY
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-03 UTC."],[],[],null,["# Using the Evaluate API\n======================\n\n|\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThe page explains how to use the Evaluate API to let your client applications\nevaluate the maliciousness of a URL. This API returns a confidence score that\nindicates the maliciousness of a URL based on blocklists, machine learning\nmodels and heuristic rules. If you want a binary result instead of a confidence\nscore, use the [Lookup API](/web-risk/docs/lookup-api).\n\n**Note:** Any URLs submitted to the Evaluate API may undergo additional processing, including crawls.\n\nBefore you begin\n----------------\n\n[Contact our sales team](https://go.chronicle.security/webriskapi) or your customer\nengineer to obtain access to this feature.\n\nEvaluating URLs\n---------------\n\nTo evaluate a URL, send an HTTP `POST` request to\nthe [`evaluateUri`](/web-risk/docs/reference/rest/v1eap1/TopLevel/evaluateUri)\nmethod. Understand the following considerations when evaluating URLs:\n\n- The Evaluate API supports one URL per request. If you want to check multiple URLs, send a separate request for each URL.\n- The URL must be valid and doesn't need to be canonicalized. For more information, see [RFC 2396](http://www.ietf.org/rfc/rfc2396.txt).\n- The Evaluate API supports three threatTypes: SOCIAL_ENGINEERING, MALWARE and UNWANTED_SOFTWARE.\n- Deprecated. The `allow_scan` field was used to determine whether Web Risk is allowed to scan the URL provided. This functionality can no longer be disabled in the Evaluate API. See the [Lookup](/web-risk/docs/lookup-api) and [Update](/web-risk/docs/update-api) APIs for crawl-free options.\n- The HTTP `POST` response returns a confidence score for the specified threatType. The confidence score represents the confidence level indicating how risky the specified URL is.\n\n### API request\n\n\nBefore using any of the request data,\nmake the following replacements:\n\u003cvar translate=\"no\"\u003eURL\u003c/var\u003e: a URL that needs to be evaluated.\n\n\nHTTP method and URL:\n\n```\nPOST https://webrisk.googleapis.com/v1eap1:evaluateUri?key=API_KEY\n```\n\n\nRequest JSON body:\n\n```\n{\n \"uri\": \"URL\",\n \"threatTypes\": [\"SOCIAL_ENGINEERING\", \"MALWARE\", \"UNWANTED_SOFTWARE\"]\n}\n```\n\nTo send your request, choose one of these options: \n\n#### curl\n\n\nSave the request body in a file named `request.json`,\nand execute the following command:\n\n```\ncurl -X POST \\\n -H \"Content-Type: application/json; charset=utf-8\" \\\n -d @request.json \\\n \"https://webrisk.googleapis.com/v1eap1:evaluateUri?key=API_KEY\"\n```\n\n#### PowerShell\n\n\nSave the request body in a file named `request.json`,\nand execute the following command:\n\n```\n$headers = @{ }\n\nInvoke-WebRequest `\n -Method POST `\n -Headers $headers `\n -ContentType: \"application/json; charset=utf-8\" `\n -InFile request.json `\n -Uri \"https://webrisk.googleapis.com/v1eap1:evaluateUri?key=API_KEY\" | Select-Object -Expand Content\n```\n\nYou should receive a JSON response similar to the following:\n\n```\n{\n \"scores\": [\n {\n \"threatType\": \"MALWARE\",\n \"confidenceLevel\": \"EXTREMELY_HIGH\"\n },\n {\n \"threatType\": \"SOCIAL_ENGINEERING\",\n \"confidenceLevel\": \"SAFE\"\n },\n {\n \"threatType\": \"UNWANTED_SOFTWARE\",\n \"confidenceLevel\": \"SAFE\"\n }\n ]\n}\n```"]]