Fetch verification options
Reports the verification methods Google currently offers for the location. Non-mutating (nothing is sent to the business). languageCode is required; service-area ("CUSTOMER_LOCATION_ONLY") businesses also require context.address, otherwise Google returns 400.
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Path Parameters
The Zernio account ID (from /v1/accounts)
Query Parameters
Override which location to query. If omitted, uses the account's selected location.
1 <= lengthRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.gmbverifications.fetchGoogleBusinessVerificationOptions({ path: { accountId: 'account_abc123', }, body: { languageCode: 'en-US', },});console.log(data);{ "success": true, "accountId": "string", "locationId": "string", "options": [ { "verificationMethod": "ADDRESS", "phoneNumber": "string" } ]}Get verification state
Returns the location's Voice of Merchant state plus its verification history. `voiceOfMerchantState.hasVoiceOfMerchant` tells you whether the listing is verified and published; when it is false, `verify` reports whether a verification is already pending. Each entry in `verifications` has a `state` of PENDING, COMPLETED, or FAILED.
Start a verification
Starts a verification for the location. This is a mutating action: depending on `method`, Google mails a postcard, places a call, or sends an SMS/email to the business. Submit the resulting code with POST /gmb-verifications/{verificationId}/complete. Use POST /gmb-verifications/options first to discover which methods are eligible.