The API output has changed, it has a new (undocumented) format. The old beta API is still there if you need the results to be the same as they were before the new format, the old beta api can be reached like http ://api.gigapan.org/beta/gigapans/’ + gigapanId + ’.json Please do not remove it!!!

We are not planning on deprecating the old API or api.gigapan.org. Currently it gives somewhat stale data but we are actively working at fixing this.

Please let us know what changes have been made already.

Absolutely. We’ll post notification here.

The api call to generate a thumbnail doesn’t seem to be working. Eg http://api.gigapan.org/beta/gigapans/44337-596×...

Thanks Ben, I’ll report this.

A year ago, with generous help from the gigapan team, I created a web page which used the gigapan API to fetch statistics about my gigapans. Of course it’s broke now. The page is described here (http://fastie.net/?page_id=480) although the links produce empty pages now. This is the line that returned a pile of json data:

“”ext_scr" type=“text/javascript” src=“http://api.gigapan.org/beta/gigapans/page/1/per_page/100/username/cfastie/most_recent.json?callback=process_json”>

How should I change the URL so it works again?

Thanks

Hi Chris,

Your code is fine, and you can’t change it to fix it.

The problem is that the called API is no longer delivering JSONP, but just JSON data, that is, it is not returning the results in a javascript callback wrapper anymore.

What is the difference between JSON and JSONP? Well, not much, but it is critical for javascript. JSONP wraps the results into a variable name so that the browsers javascript engine can execute it. The problem has to do with the data being cross domain, if you were serving the results from your own domain, the javascript libraries could access it, but they can only access the data cross domain if it is in a variable wrapper.

JSON example:

{"name":“Ant”,‘gigapixels’: ‘0.0170898’}

JSONP example:

gigapan={"name":“Ant”,‘gigapixels’: ‘0.0170898’

Thanks

JaSON

Hi Chris and Jason,

Sorry for the problem. Jason, your analysis is correct — we appear to not be supporting JSONP correctly, even though we intend to. Hang tight while we work on a fix for this.

— Randy

JSONP calls to api.gigapan.org/beta/(.*).json?callback=foobar should now work as expected.

The thumbnailing API to api.gigapan.org/beta should also work again (e.g. http://api.gigapan.org/beta/gigapans/44337-596×...)

Awesome, thank you for fixing this, and so fast too!!!!

Thanks, everyone for getting this back to normal. My statistics pages are working again. Now all we need is for the statistics to be updated ;)

I guess my statistics pages are not quite back to normal. Although I have about 90 public gigapans, my call to the API is returning only 60. The URL I am using is:
h_tp://api.gigapan.org/beta/gigapans/page/1/per_page/100/username/cfastie/most_recent.json?callback=process_json

The “jdata.per_page” variable is apparently coming back equal to 60, even though the URL tries to set it to 100.

This must be due to a change in the way the API works. Is there a way to get all 90 gigapans returned in one page?

Thanks

Hi Chris,

This is a bug in our legacy support and we’ll definitely get around to fixing it. No ETA though. More than a week, less than a year.