google_api_safe_browsing v0.1.0 API Reference
Modules
API calls for all endpoints tagged EncodedFullHashes
API calls for all endpoints tagged EncodedUpdates
API calls for all endpoints tagged FullHashes
API calls for all endpoints tagged ThreatHits
API calls for all endpoints tagged ThreatListUpdates
API calls for all endpoints tagged ThreatLists
API calls for all endpoints tagged ThreatMatches
Handle Tesla connections for GoogleApi.SafeBrowsing.V4
Helper functions for deserializing responses into models
The expected state of a client's local database
The client metadata associated with Safe Browsing API requests
The constraints for this update
A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for `Empty` is empty JSON object `{}`
Describes a Safe Browsing API update request. Clients can request updates for multiple lists in a single request. NOTE: Field index 2 is unused. NEXT: 5
Request to return full hashes matched by the provided hash prefixes
Request to check entries against lists
A single list update request
An update to an individual list
A single metadata entry
The uncompressed threat entries in hash format of a particular prefix length. Hashes can be anywhere from 4 to 32 bytes in size. A large majority are 4 bytes, but some hashes are lengthened if they collide with the hash of a popular URL. Used for sending ThreatEntrySet to clients that do not support compression, or when sending non-4-byte hashes to clients that do support compression
A set of raw indices to remove from a local list
The Rice-Golomb encoded data. Used for sending compressed 4-byte hashes or compressed removal indices
An individual threat; for example, a malicious URL or its hash representation. Only one of these fields should be set
The metadata associated with a specific threat entry. The client is expected to know the metadata key/value pairs associated with each threat type
A set of threats that should be added or removed from a client's local database
The information regarding one or more threats that a client submits when checking for matches in threat lists
Describes an individual threat list. A list is defined by three parameters: the type of threat posed, the type of platform targeted by the threat, and the type of entries in the list
A match when checking a threat entry in the Safe Browsing threat lists
A single resource related to a threat hit
Details about the user that encountered the threat
Helper functions for building Tesla requests