Wednesday, December 9, 2020<\/p>\n
\nA few months ago we announced an API infrastructure upgrade<\/a> \nIf you make your own calls to the API, read on.\n<\/p>\n \n The Performance report<\/a> already supports fresh data that is less than a day old. You can now access this data through the API by passing the request parameter \nA few months ago, we added a News tab on Search filter<\/a> to the \nThe Sitemaps API now supports domain properties, as other Search Console APIs already do. You can query, add, and delete your sitemaps on \nWe’ll drop the support in the Webmasters discovery document. If you’re querying the Search Console API using an external API library<\/a>, or querying \nFor updates on the API library changes, refer to the Java<\/a> and \nFor all Webmasters service-related imports, change the <\/span> <\/span> <\/span> <\/span> \nNote that besides the service object, other API objects are exactly the same as before, only the package<\/strong> changes.\n<\/p>\n \nWhen building the Webmasters service object, make the following change:\n<\/p>\n <\/span> <\/span> \nAgain, there’s no change in how objects behave.\n<\/p>\n \nThe discovery document querying changes include:\n<\/p>\n <\/span> <\/span> \nIf you have any questions, you can ask in the Buscar \n
\n to improve the performance of the Search Console API<\/a> as demand grows. Today we’re happy to announce
\n some more updates coming your way:\n<\/p>\n\n
Fresh data and news filter in the Search Console API<\/h2>\n
\n dataState<\/code> with value set to all<\/code>. The data you get for this value will also include fresh data that is not yet final. If you wish to get only final data,
\n you can either pass this parameter with value set to final<\/code> or not pass it at all and you will get only final data by default.\n<\/p>\n
\n Performance report. This information is now also available in the API, and you can access it by setting the value of searchType<\/code>
\n parameter in the request to news<\/code>.\n<\/p>\nDomain property support in the Sitemaps API<\/h2>\n
\n domain properties<\/a>, for example:\n<\/p>\nGET https:\/\/www.googleapis.com\/webmasters\/v3\/sites\/sc-domain:example.com\/sitemaps<\/code><\/p>\nDiscovery doc migration<\/h2>\n
\n the Webmasters API discovery document<\/a> directly, you will
\n need to update your API calls to include the following changes.\n<\/p>\nAPI library changes<\/h3>\n
\n Python<\/a> quickstart guides,
\n for an updated API usage guide.\n<\/p>\nJava<\/h4>\n
webmasters<\/code> package to the searchconsole.v1<\/code> package,
\n and the service name, Webmasters<\/code>, to SearchConsole<\/code>. Examples:\n<\/p>\n\n
import com.google.api.services.webmasters.Webmasters;<\/code><\/p>\nimport com.google.api.services.searchconsole.v1.SearchConsole;<\/code><\/p>\n<\/li>\nimport com.google.api.services.webmasters.model.WmxSite;<\/code><\/p>\nimport com.google.api.services.searchconsole.v1.model.WmxSite;<\/code><\/p>\n<\/li>\n<\/ul>\nPython<\/h4>\n
webmasters_service = build('webmasters', 'v3', http=http)<\/code><\/p>\nwebmasters_service = build('searchconsole', 'v1', http=http)<\/code><\/p>\nDirect discovery document query<\/h3>\n
\n
https:\/\/www.googleapis.com\/discovery\/v1\/apis\/webmasters\/v3\/rest<\/code><\/p>\nhttps:\/\/searchconsole.googleapis.com\/$discovery\/rest<\/code><\/p>\n<\/li>\n\n
name<\/code> field changed from webmasters<\/code> to searchconsole<\/code>.<\/li>\nversion<\/code> field changed from v3<\/code> to v1<\/code>.<\/li>\n<\/ul>\n<\/ul>\n
\n Central community<\/a> o on Twitter<\/a>.\n<\/p>\n