Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Menggunakan Submission API
Dokumen ini menjelaskan cara mengirimkan URL yang Anda curigai tidak aman ke
Safe Browsing untuk dianalisis, dan memeriksa hasil pengiriman
ini secara asinkron. Setiap URL yang dikonfirmasi melanggar Kebijakan Safe Browsing
akan ditambahkan ke layanan Safe Browsing.
Web Risk Submission API memvalidasi bahwa URL yang dikirim menampilkan konten yang melanggar kebijakan Safe Browsing. Developer API harus memastikan bahwa URL yang dikirim memiliki bukti yang jelas bahwa URL tersebut melanggar kebijakan ini. Contoh berikut menunjukkan bukti pelanggaran kebijakan:
Konten manipulasi psikologis yang meniru merek online yang sah (nama merek, logo, tampilan dan nuansa), pemberitahuan sistem, menggunakan URL yang menipu, atau meminta pengguna memasukkan kredensial sensitif seperti nama pengguna atau sandi.
Situs yang menghosting Malware yang dapat dieksekusi dan diketahui.
Developer API tidak boleh mengirimkan jenis URL ini, karena kemungkinan besar URL tersebut tidak akan ditambahkan ke daftar blokir Safe Browsing:
Survei palsu, situs belanja, atau scam lainnya yang tidak menunjukkan phishing (seperti scam mata uang kripto).
Spam yang berisi konten perjudian, kekerasan, atau konten khusus dewasa yang bukan phishing atau malware.
Mengirim URL
Untuk mengirimkan URL, kirim permintaan POST HTTP ke metode projects.uris.submit.
Submission API mendukung satu URL per permintaan. Untuk memeriksa beberapa URL, Anda
harus mengirim permintaan terpisah untuk setiap URL.
URL harus valid, tetapi tidak perlu dikanonikasikan. Untuk mengetahui informasi
selengkapnya, lihat RFC 2396.
Respons POST HTTP menampilkan long-running operation.
Untuk mengetahui informasi selengkapnya tentang cara mengambil hasil pengiriman dan memeriksa
status pengiriman, lihat Operasi yang berjalan lama.
Contoh
Metode HTTP dan URL:
POST https://webrisk.googleapis.com/v1/projects/project-id/uris:submit
SUCCEEDED menunjukkan bahwa URL yang dikirim telah ditambahkan ke Daftar URL yang Tidak Diizinkan
Safe Browsing.
CLOSED menunjukkan bahwa URL yang dikirim tidak terdeteksi melanggar Kebijakan
Safe Browsing dan tidak ditambahkan ke Daftar yang Tidak Diizinkan Safe Browsing dalam
24 jam terakhir.
[[["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-08-17 UTC."],[],[],null,["# Using the Submission API\n========================\n\nThis document describes how to submit URLs that you suspect are unsafe to\nSafe Browsing for analysis, and asynchronously check the results of these\nsubmissions. Any URLs that are confirmed to violate the [Safe Browsing Policies](https://safebrowsing.google.com/#policies)\nare added to the Safe Browsing service.\n\nBefore you begin\n----------------\n\n[Contact sales](https://cloud.google.com/contact) or your customer engineer in order to obtain access to\nthis feature.\n\nBest Practices\n--------------\n\n### Read the [Safe Browsing Policies](https://safebrowsing.google.com/#policies)\n\nThe Web Risk Submission API validates that the submitted URLs render content violating Safe Browsing [policies](https://safebrowsing.google.com/#policies). API developers must ensure that the submitted URLs have clear evidence of violating these policies. The following examples show evidences of violation of policies:\n\n- Social engineering content that mimics a legitimate online brand (brand name, logo, look and feel), system alerts, uses deceptive URLs, or requests users to enter sensitive credentials such as a username or password.\n- A site that is hosting a known Malware executable.\n\nAPI developers should not submit these types of URLs, as they most likely will not be added to Safe Browsing blocklists:\n\n- Fake surveys, shopping sites, or other scams that do not demonstrate phishing (such as cryptocurrency scams).\n- Spam containing gambling, violence, or adult content that is not phishing or malware.\n\nSubmit URLs\n-----------\n\nTo submit a URL, send an HTTP `POST` request to\nthe [`projects.uris.submit`](/web-risk/docs/reference/rest/v1/projects.uris/submit)\nmethod.\n\n- The Submission API supports one URL per request. To check multiple URLs, you need to send a separate request for each URL.\n- The URL must be valid but it doesn't need to be canonicalized. For more\n information, see [RFC 2396](http://www.ietf.org/rfc/rfc2396.txt).\n\n- The HTTP `POST` response returns a [`long-running operation`](/web-risk/docs/reference/rpc/google.longrunning).\n For more information about how to retrieve the submission result and check\n the status of a submission, see [Long-running operations](/web-risk/docs/long-running-operations).\n\nExample\n-------\n\n\nHTTP method and URL:\n\n```\nPOST https://webrisk.googleapis.com/v1/projects/project-id/uris:submit\n```\n\n\nRequest JSON body:\n\n```\n{\n \"submission\": {\n \"uri\": \"https://www.example.com/login.html\"\n }\n}\n```\n\nTo send your request, choose one of these options: \n\n#### curl\n\n| **Note:** The following command assumes that you have logged in to the `gcloud` CLI with your user account by running [`gcloud init`](/sdk/gcloud/reference/init) or [`gcloud auth login`](/sdk/gcloud/reference/auth/login) , or by using [Cloud Shell](/shell/docs), which automatically logs you into the `gcloud` CLI . You can check the currently active account by running [`gcloud auth list`](/sdk/gcloud/reference/auth/list).\n\n\nSave the request body in a file named `request.json`,\nand execute the following command:\n\n```\ncurl -X POST \\\n -H \"Authorization: Bearer $(gcloud auth print-access-token)\" \\\n -H \"Content-Type: application/json; charset=utf-8\" \\\n -d @request.json \\\n \"https://webrisk.googleapis.com/v1/projects/project-id/uris:submit\"\n```\n\n#### PowerShell\n\n| **Note:** The following command assumes that you have logged in to the `gcloud` CLI with your user account by running [`gcloud init`](/sdk/gcloud/reference/init) or [`gcloud auth login`](/sdk/gcloud/reference/auth/login) . You can check the currently active account by running [`gcloud auth list`](/sdk/gcloud/reference/auth/list).\n\n\nSave the request body in a file named `request.json`,\nand execute the following command:\n\n```\n$cred = gcloud auth print-access-token\n$headers = @{ \"Authorization\" = \"Bearer $cred\" }\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/v1/projects/project-id/uris:submit\" | Select-Object -Expand Content\n```\n\nYou should receive a JSON response similar to the following:\n\n```\n{\n \"name\": \"projects/project-number/operations/operation-id\",\n}\n```\n\n### Check the submission status\n\nYou can [check the status of the submission](/web-risk/docs/long-running-operations#get)\nby using the `project-number` and `operation-id` values from the response.\n\n`SUCCEEDED` indicates that the submitted URL was added to the Safe Browsing\nBlocklist.\n\n`CLOSED` indicates that the submitted URL was not detected to violate the Safe\nBrowsing Policies and was not added to the Safe Browsing Blocklist in the last\n24 hours."]]
