Help protect your website from fraudulent activity, spam, and abuse without creating friction.

Defines the root interface for all clients that generate credentials for calling Google APIs. All clients should implement this interface.

Account defender risk assessment.

Information about account verification, used for identity verification.

Settings specific to keys that can be used by Android apps.

The request message to annotate an Assessment.

Empty response for AnnotateAssessment.

Contains fields that are required to perform Apple-specific integrity checks.

A reCAPTCHA Enterprise assessment resource.

Metrics related to challenges.

Information about a verification endpoint that can be used for 2FA.

The event being assessed.

An individual action. Each action represents what to do if a policy matches.

An allow action continues processing a request unimpeded.

A block action serves an HTTP error code a prevents the request from hitting the backend.

An include reCAPTCHA script action involves injecting reCAPTCHA JavaScript code into the HTML returned by the site backend. This reCAPTCHA script is tasked with collecting user signals on the requested web page, issuing tokens as a cookie within the site domain, and enabling their utilization in subsequent page requests.

A redirect action returns a 307 (temporary redirect) response, pointing the user to a ReCaptcha interstitial page to attach a token.

A set header action sets a header and forwards the request to the backend. This can be used to trigger custom protection implemented on the backend.

A substitute action transparently serves a different page than the one requested.

A FirewallPolicy represents a single matching pattern and resulting actions to take.

Policy config assessment.

Assessment for Fraud Prevention.

Information about behavioral trust of the transaction.

Information about card testing fraud, where an adversary is testing fraudulently obtained cards or brute forcing their details.

Information about stolen instrument fraud, where the user is not the legitimate owner of the instrument being used for the purchase.

Fraud signals describing users and cards involved in the transaction.

Signals describing the payment card used in this transaction.

Signals describing the user involved in this transaction.

Settings specific to keys that can be used by iOS apps.

A key used to identify and configure applications (web and/or mobile) that use reCAPTCHA Enterprise.

Response to request to list firewall policies belonging to a project.

Response to request to list keys in a project.

The response to a ListRelatedAccountGroupMemberships call.

The response to a ListRelatedAccountGroups call.

Metrics for a single Key.

The migrate key request message.

Private password leak verification info.

A group of related accounts.

A membership in a group of related accounts.

The reorder firewall policies request message.

The reorder firewall policies response message.

Secret key is used only in legacy reCAPTCHA. It must be used in a 3rd party integration with legacy reCAPTCHA.

Risk analysis result for an event.

Score distribution.

Metrics related to scoring.

The request message to search related account group memberships.

The response to a SearchRelatedAccountGroupMemberships call.

Options for user acceptance testing.

Properties of the provided event token.

Transaction data associated with a payment protected by reCAPTCHA Enterprise.

Structured address format for billing and shipping addresses.

Details about the transaction from the gateway.

Line items being purchased in this transaction.

Details about a user's account involved in the transaction.

Describes an event in the lifecycle of a payment transaction.

An identifier associated with a user.

User information associated with a request protected by reCAPTCHA Enterprise.

Settings specific to keys that can be used for WAF (Web Application Firewall).

Settings specific to keys that can be used by websites.

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 Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

Additional options for reCAPTCHAEnterprise#projectsFirewallpoliciesList.

Additional options for reCAPTCHAEnterprise#projectsFirewallpoliciesPatch.

Additional options for reCAPTCHAEnterprise#projectsKeysList.

Additional options for reCAPTCHAEnterprise#projectsKeysPatch.

Additional options for reCAPTCHAEnterprise#projectsRelatedaccountgroupsList.

Additional options for reCAPTCHAEnterprise#projectsRelatedaccountgroupsMembershipsList.