JSONP with jQuery, MooTools, and Dojo

By  on  

JSONP MooTools jQuery

We all know that the big limitation of AJAX is that cross-domain requests aren't allowed.  We also know, however, that we skirt around that rule a bit by using JSONP.  JSONP is the process of SCRIPT tag injection, referencing a cross-domain URL and providing a callback function (on your page) that the provider will call so that you can handle the result.  Let's take a look at how JSONP is handled with jQuery, MooTools, and the Dojo Toolkit.  For our examples, we'll pull tweets from Twitter with the term "Arsenal" in them.

jQuery JSONP

jQuery uses the same method for JSONP as it does for regular JSON -- the jQuery.getJSON method:

	q: "Arsenal"
},function(tweets) {
	// Handle response here
	console.info("Twitter returned: ",tweets);

As long as a callback parameter is provided to the getJSON method, jQuery will consider the request JSONP.

MooTools JSONP

MooTools requires the Request.JSONP Class available in MooTools More.  Armed with Request.JSONP, fetching JSON from another domain is a piece of cake:

new Request.JSONP({
	url: "http://search.twitter.com/search.json",
	data: {
		q: "Arsenal"
	onComplete: function(tweets) {
		// Log the result to console for inspection
		console.info("Twitter returned: ",tweets);

Request.JSONP is a super compact class too!


JSONP with the Dojo Toolkit requires the dojo.io.script resource and its get method:

// dojo.io.script is an external dependency, so it must be required

// When the resource is ready
dojo.ready(function() {
	// Use the get method
		// The URL to get JSON from Twitter
		url: "http://search.twitter.com/search.json",
		// The callback paramater
		callbackParamName: "callback", // Twitter requires "callback"
		// The content to send
		content: {
			q: "Arsenal"
		// The success callback
		load: function(tweetsJson) {  // Twitter sent us information!
			// Log the result to console for inspection
			console.info("Twitter returned: ",tweetsJson);

Retrieving JSON with Dojo is usually done with the dojo.xhrGet method, but JSONP request this special method.  The arguments for dojo.io.script.get are the same as dojo.xhrGet with the exception of the callback parameter.

JSONP is a hugely effective, reliable, and easy to implement.  JSONP strategies also allow developers to avoid cumbersome server-side proxy writing to retrieve data.  Each of the JavaScript libraries above have battle-tested methods for retrieving JSON data across domains -- it's up to you to implement them to suit your needs!

Recent Features

  • By
    CSS Animations Between Media Queries

    CSS animations are right up there with sliced bread. CSS animations are efficient because they can be hardware accelerated, they require no JavaScript overhead, and they are composed of very little CSS code. Quite often we add CSS transforms to elements via CSS during...

  • By
    How to Create a Twitter Card

    One of my favorite social APIs was the Open Graph API adopted by Facebook.  Adding just a few META tags to each page allowed links to my article to be styled and presented the way I wanted them to, giving me a bit of control...

Incredible Demos

  • By
    pointer Media Query

    As more devices emerge and differences in device interaction are implemented, the more important good CSS code will become.  In order to write good CSS, we need some indicator about device capabilities.  We've used CSS media queries thus far, with checks for max-width and pixel ratios.

  • By
    Create a Trailing Mouse Cursor Effect Using MooTools

    Remember the old days of DHTML and effects that were an achievement to create but had absolutely no value? Well, a trailing mouse cursor script is sorta like that. And I'm sorta the type of guy that creates effects just because I can.


  1. Cool! Thanks for sharing! :)

  2. In my plugd project I have a script.js plugin, which provides functionality similar to $.getJSON without requiring io.script (though doesn’t use the same Promises all other Dojo IO things use)

  3. For those interested, Pete’s plugd can be found at: https://github.com/phiggins42/plugd

  4. the only way i could make it work was this

      url: url,
      dataType: 'jsonp',
      data: parameters,
      complete:function(jqXHR, textStatus){
          console.log("Ajax completado. ");
      success: function(data, textStatus, jqXHR){
          if(console !=undefined)
      error:function(jqXHR, textStatus, errorThrown){
          console.log("Error: "+textStatus+errorThrown);
  5. wooop. Thanks David you animal

  6. Vic

    now we still need a clever way to make POST requests using cross domain ajax calls, I think there are some initiatives around called jsonp tunnels

  7. Lolki

    Euh, what is Arsenal ?

    :) just kidding ! ;)

  8. Thomas

    It is worth noting that these examples only work as the jsonp files you are requesting are generated dynamically, that is why you need the callback=?.

    If you are trying to load in static json files, say from a CDN you will need to wrap you json data in something like this myFunction({ [ "data" : "value"] });

    Then in your js file you need your ajax call, and a function that has the same name as your wrapper in the json file.

     $.ajax({url: "http://otherdomain.com/json.json",dataType: "jsonp",cache: false,jsonp:'onJsonPLoad',jsonpcallbackString: "myFunction"}) ;
    // callback function
    // do stuff with the json data

    Of course, if you have access to PHP on the server that is dishing up your JSON files you can have the jsonp file like this

    And David’s methods will work a treat.

    • Thomas

      Forgot to wrap the php bit

    • Thomas

      echo $_GET['callback'] .'({["data" : "value" ]})';

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!