Troubleshoot Site Verification API issues
This page describes some common issues that you might encounter involving the
Site Verification API as a reseller.
400:badRequest
This error occurs when Google can't find the verification token. To resolve this
issue, verify that token has been successfully placed in the destination and
continue to call this method with backoff delay until you receive a 200
response.
400:invalidParameter
This error occurs when the verification token is invalid. Call the
webResource.getToken method to get a valid token.
403:usageLimits.dailyLimitExceeded
This error occurs when you've reached the daily quota for calls to this API. To
resolve this issue, implement a backoff delay. For more information, see
Usage limits and quotas.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-12-19 UTC.
[null,null,["Last updated 2024-12-19 UTC."],[[["Resellers using the Site Verification API might encounter issues such as Google not finding the verification token, an invalid verification token, or exceeding the daily usage quota."],["A `400:badRequest` error indicates an unverified token and requires placement confirmation and continued API calls with backoff delays."],["An `400:invalidParameter` error signifies an invalid token necessitating the retrieval of a valid token using the `webResource.getToken` method."],["A `403:usageLimits.dailyLimitExceeded` error implies exceeding the daily call quota, requiring implementation of backoff delays and consulting usage limit documentation for further information."]]],[]]
