Introducing new Fusion Tables API by Warren Shen.
The post in its entirety:
We are very pleased to announce the public availability of the new Fusion Tables API. The new API includes all of the functionality of the existing SQL API, plus the ability to read and modify table and column metadata as well as the definitions of styles and templates for data visualization. This API is also integrated with the Google APIs console which lets developers manage all their Google APIs in one place and take advantage of built-in reporting and authentication features.
With this launch, we are also announcing a six month deprecation period for the existing SQL API. Since the new API includes all of the functionality of the existing SQL API, developers can easily migrate their applications using our migration guide.
For a detailed description of the features in the new API, please refer to the API documentation.
BTW, if you go to the Migration Guide, be aware that as of 27 June 2012, the following links aren’t working (404):
This Migration Guide documents how to convert existing code using the SQL API to code using the Fusion Tables API 1.0. This information is discussed in more detail in the Getting Started and Using the API developer guides.
I have discovered the error:
https://developers.google.com/fusiontables/docs/v1/v1/getting_started.html – Wrong – note the successive “/v1.”
https://developers.google.com/fusiontables/docs/v1/getting_started – Correct – From the left side nav. bar.
https://developers.google.com/fusiontables/docs/v1/v1/using.html – Wrong – note the successive “/v1.”
https://developers.google.com/fusiontables/docs/v1/using – Correct – From the left side nav. bar.
The summary material appears to be useful but you will need the more detailed information as well.
For example, under HTTP Methods (in the Migration Guide), the SQL API is listed as having:
GET for SHOW TABLES, DESCRIBE TABLE, SELECT
And the equivalent in the Fusion API:
GET for SELECT
No equivalent of SHOW TABLES, DESCRIBE TABLE using GET.
If you find and read Using the API you will find:
Retrieving a list of tables
Listing tables is useful because it provides the table ID and column names of tables that are necessary for other calls. You can retrieve the list of tables a user owns by sending an HTTP GET request to the URI with the following format:
Tables are listed along with column ids, names and datatypes.
That may be too much for the migration document but implying that all you have with
SELECT is misleading.
GET for TABLES (SHOW + DESCRIBE), SELECT