The Google Fusion Tables API will not be available after Dec. 3, 2019. Learn more


Issues and solutions

"Not found" message for an incorrect API Key parameter

If you are using Google Fusion Tables API to write a URL that you can run from the browser and you obtain a Not Found message, you may want to double-check the format of your URL. You may have preceded the API key parameter with a "?" or "&" incorrectly. See Getting Started for more information and some examples.


"403: Daily Limit Exceeded" message for a missing API Key

If you do not include an API Key, you will receive a "403: Daily Limit Exceeded" message. For example, if you put this in your browser, you'll get a 403 error:

Add your API key into the URL, such as ?key=AIzaSyAm9yWCV7JPCTHCJut8whOjARd7pwROFDQ, and it will work. See Getting Started for more information and some examples.


Map tiles show "Data may still be loading" message

Cause: Some users note latency in the map being displayed when a table loads for the first time.

Refresh the page.
Redisplay the map to flush cached tiles. You may need to wait 10-30 seconds before the map appears. As more people view the map, this latency goes away.


Map tiles "Data may still be loading" message does not resolve

Cause: Google Fusion Tables is unable to understand the query in the FusionTableLayer. A few things to try:

Check the query object syntax.
Any syntax error can trigger this error message. To resolve it, fix your Google Fusion Tables Layers syntax. See FusionTableLayer documentation at Google Maps JavaScript API v3 Reference and Google Maps JavaScript API Layers
Check the table ID.
Double-check that you are using the correct table ID.
Check column names.
Column names are case-sensitive, so "Zipcode" and "zipcode" are not the same. Multi-word column names need to be enclosed in single quotes. See API v2.0: SQL Reference.
Check your geocoding.
Google Fusion Tables must understand the locations in your table before it can map them. Location descriptions in your table, such as addresses, must be geocoded. See "Geocoding Location Descriptions" in the Google Fusion Tables Developer's Guide.

Note: You may find it helpful to subscribe to the Google Fusion Tables API Users Group, which often has useful content and shared comments from other developers.