Google Business Verification
Verify a Google Business Profile location without leaving your app, and find out why a location cannot publish (suspended, unverified, duplicate, under review). These endpoints call Google's My Business Verifications API.
- Authentication: API Key —
Authorization: Apikey <YOUR_API_KEY> location_idfollows the same rules as Location Info ("Which location?").
Steps 1, 2 and 5 (state, options, list) are available. Starting a verification, entering the code and
the instant token are not generally available yet: until then they answer 503 gbp_feature_disabled.
If the feature is not available on your account yet, every endpoint answers
503 with error_code: google_api_not_enabled. Try again later.
1. Check the location's state
GET /api/uploadposts/google-business/verification/state?user=my-shop[&location_id=]
{
"success": true,
"location_id": "locations/111",
"summary": { "status": "unverified", "action": "Verify the location: see the options with POST /api/uploadposts/google-business/verification/options." },
"state": { "verify": { "hasPendingVerification": false } }
}
summary.status: ok, unverified, verification_pending, suspended, disabled, duplicate,
under_review or unknown. state is Google's
VoiceOfMerchantState as is.
2. See the available methods
POST /api/uploadposts/google-business/verification/options
| Field | Required | Description |
|---|---|---|
user | Yes | Profile username. |
location_id | No | Location. |
language_code | No | BCP-47, default en. The methods depend on the language and the country. |
context | No | Only for service-area businesses without a storefront: {"address": {PostalAddress with regionCode}}. |
{
"success": true,
"location_id": "locations/111",
"options": [
{ "verificationMethod": "SMS", "phoneNumber": "+34 600 000 000" },
{ "verificationMethod": "ADDRESS", "addressData": { "business": "My Shop", "expectedDeliveryDaysRegion": 12 } }
]
}
3. Start a verification
POST /api/uploadposts/google-business/verification/start
Google contacts the business (postcard, SMS, call or email), so the body must carry "confirm": true;
without it the API answers 400 confirmation_required and nothing happens.
Each location can start 3 verifications a day (429 daily_limit_reached with scope: location).
| Field | Required | Description |
|---|---|---|
user, location_id | Yes / No | As above. |
method | Yes | ADDRESS, EMAIL, PHONE_CALL, SMS, AUTO or TRUSTED_PARTNER (one of the options of step 2). |
phone_number | No | PHONE_CALL / SMS: one of the numbers in the options. |
email_address | No | EMAIL: one of the addresses in the options. |
mailer_contact | No | ADDRESS: name the postcard is addressed to. |
trusted_partner_token | Conditional | Required for TRUSTED_PARTNER. |
token | No | Vetted partners only. Cannot be combined with phone_number, email_address, mailer_contact or trusted_partner_token (400 conflicting_verification_inputs). |
language_code, context | No | As in step 2. |
confirm | Yes | true. |
curl -X POST https://api.upload-post.com/api/uploadposts/google-business/verification/start \
-H 'Authorization: Apikey YOUR_API_KEY' -H 'Content-Type: application/json' \
-d '{"user": "my-shop", "method": "SMS", "phone_number": "+34 600 000 000", "confirm": true}'
{ "success": true, "location_id": "locations/111",
"verification_name": "locations/111/verifications/7", "state": "PENDING",
"verification": { "name": "locations/111/verifications/7", "method": "SMS", "state": "PENDING" } }
AUTO verifications are COMPLETED at once; the others wait for the code.
4. Enter the code
POST /api/uploadposts/google-business/verification/complete
| Field | Required | Description |
|---|---|---|
user | Yes | Profile username. |
verification_name | Yes* | locations/{l}/verifications/{v} from step 3 or the list. |
verification_id | Yes* | Alternative: the last part of the name, with location_id. |
pin | Yes | The code Google sent. |
10 attempts a day per account and location (429 daily_limit_reached); only codes Google actually checked count.
Answer: state: COMPLETED when Google accepts the code.
5. List verifications
GET /api/uploadposts/google-business/verifications?user=my-shop[&location_id=&page_size=1-100&page_token=]
{ "success": true, "location_id": "locations/111",
"verifications": [{ "name": "locations/111/verifications/7", "method": "SMS", "state": "PENDING", "createTime": "..." }],
"next_page_token": null }
Instant verification token
POST /api/uploadposts/google-business/verification/token with {"user": "...", "location_id": "..."}
asks Google for an instant verification token. When Google answers that the token is reserved to its
vetted partners, the API answers 403 partner_only; use step 3 instead.
Errors
success: false with code and error_code:
400 confirmation_required, invalid_verification_method, invalid_phone_number, invalid_email_address,
invalid_mailer_contact, trusted_partner_token_required, invalid_language_code, invalid_context,
invalid_pin, invalid_verification_name, verification_required, invalid_page_size,
invalid_location_id, conflicting_verification_inputs, invalid_json;
403 partner_only, google_business_permission_denied; 404 verification_not_found, location_not_found;
429 daily_limit_reached (with scope, daily_limit and retry_after_seconds), google_rate_limited;
502 google_result_unknown (Google did not confirm a start or a code: check the list before trying again);
503 google_api_not_enabled, gbp_feature_disabled, gbp_quota_guard_unavailable (the daily limits cannot be
checked right now; nothing was sent to Google, try again in a few minutes).