- HTTP request
- Path parameters
- Request body
- Response body
- Authorization Scopes
- VerificationOption
- PhoneVerificationData
- AddressVerificationData
- EmailVerificationData
Reports all eligible verification options for a location in a specific language.
HTTP request
POST https://mybusiness.googleapis.com/v4/{name=accounts/*/locations/*}:fetchVerificationOptions
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
name |
Resource name of the location to verify. |
Request body
The request body contains data with the following structure:
JSON representation | |
---|---|
{
"languageCode": string,
"context": {
object ( |
Fields | |
---|---|
languageCode |
The BCP 47 language code representing the language that is to be used for the verification process. Available options vary by language. |
context |
Extra context information for the verification of service businesses. Required for the locations whose business type is CUSTOMER_LOCATION_ONLY. INVALID_ARGUMENT will be thrown if it is set for other business types of locations. |
Response body
If successful, the response body contains data with the following structure:
Response message for Verifications.FetchVerificationOptions.
JSON representation | |
---|---|
{
"options": [
{
object ( |
Fields | |
---|---|
options[] |
The available verification options. |
Authorization Scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/plus.business.manage
https://www.googleapis.com/auth/business.manage
For more information, see the OAuth 2.0 Overview.
VerificationOption
The verification option represents how to verify the location (indicated by verification method) and where the verification will be sent to (indicated by display data).
JSON representation | |
---|---|
{ "verificationMethod": enum ( |
Fields | ||
---|---|---|
verificationMethod |
Method to verify the location. |
|
Union field DisplayData . One of the display data. The data must match the method. Empty if the corresponding method doesn't have any display data. DisplayData can be only one of the following: |
||
phoneData |
Set only if the method is PHONE_CALL or SMS. |
|
addressData |
Set only if the method is MAIL. |
|
emailData |
Set only if the method is EMAIL. |
PhoneVerificationData
Display Data for verifications through phone, e.g. phone call, sms.
JSON representation | |
---|---|
{ "phoneNumber": string } |
Fields | |
---|---|
phoneNumber |
Phone number that the PIN will be sent to. |
AddressVerificationData
Display data for verifications through postcard.
JSON representation | |
---|---|
{
"businessName": string,
"address": {
object ( |
Fields | |
---|---|
businessName |
Merchant's business name. |
address |
Address that a postcard can be sent to. |
EmailVerificationData
Display data for verifications through email.
JSON representation | |
---|---|
{ "domainName": string, "userName": string, "isUserNameEditable": boolean } |
Fields | |
---|---|
domainName |
Domain name in the email address. e.g. "gmail.com" in foo@gmail.com |
userName |
User name in the email address. e.g. "foo" in foo@gmail.com |
isUserNameEditable |
Whether client is allowed to provide a different user name. |