Difference Between $.getJSON() and $.ajax() in jQuery

Content-type

You don’t need to specify that content-type on calls to MVC controller actions. The special “application/json; charset=utf-8” content-type is only necessary when calling ASP.NET AJAX “ScriptServices” and page methods. jQuery’s default contentType of “application/x-www-form-urlencoded” is appropriate for requesting an MVC controller action.

More about that content-type here: JSON Hijacking and How ASP.NET AJAX 1.0 Avoids these Attacks

Data

The data is correct as you have it. By passing jQuery a JSON object, as you have, it will be serialized as patientID=1 in the POST data. This standard form is how MVC expects the parameters.

You only have to enclose the parameters in quotes like “{ ‘patientID’ : 1 }” when you’re using ASP.NET AJAX services. They expect a single string representing a JSON object to be parsed out, rather than the individual variables in the POST data.

JSON

It’s not a problem in this specific case, but it’s a good idea to get in the habit of quoting any string keys or values in your JSON object. If you inadvertently use a JavaScript reserved keyword as a key or value in the object, without quoting it, you’ll run into a confusing-to-debug problem.

Conversely, you don’t have to quote numeric or boolean values. It’s always safe to use them directly in the object.

So, assuming you do want to POST instead of GET, your $.ajax() call might look like this:

$.ajax({
  type: 'POST',
  url: '/Services/GetPatient',
  data: { 'patientID' : 1 },
  dataType: 'json',
  success: function(jsonData) {
    alert(jsonData);
  },
  error: function() {
    alert('Error loading PatientID=' + id);
  }
});