Home > Articles > Web Services > XML

Beyond HTML: Returning JSON and XML Data From Your MVC Endpoints

You adopted MVC to get better control over your URL structure. Then you’re asked to provide REST access over the same data. Instead of developing a new API and set of endpoints that mirrors what you already have, you can augment the existing application to respond to requests for JSON and XML as well as handle data updates and deletes. Scott Seely shows you how.
Like this article? We recommend

Like this article? We recommend

If your web application is like many others built today, you are busy looking at how to add JSON and XML-based REST services to that application. Many of your fellow web developers are adopting ASP.NET MVC because it offers the ability to create readable URL structures for your applications. Wouldn’t it be great if, after creating the primary MVC application, you could reuse those pages to create the REST services too? After all, you are already building applications with beautiful user interfaces (UIs) that people understand how to access. You are already spending the time to create clean URL structures.

Certainly, that was true for me. I took a moment and thought, “What would I need to do to make the JSON and XML services flow from my UI efforts?”

In this article, I assume you are already familiar with MVC. I explain the differences in how computers ask for resources for presentation to people and for presentation to other code. I then explore how to use this difference to generate different resource representations, and what to do to recognize the data format the client specifies in a GET request. First, we look at what a resource actually is. We then look at Multipurpose Internet Mail Extension (MIME) types. To deliver a more complete picture of how this fits into a RESTful service, the example code shows how to implement full REST management of the data managed by the endpoint.

Getting Resources in Context

A resource is a thing: a purchase order, a book review, the list of your friends’ activities. Every resource accessible by URL has at least one representation. For example, you may have a Person resource represented by the following C# class:

public class Person
    public int Id { get; set; }
    public string FirstName { get; set; }
    public string LastName { get; set; }
    public IEnumerable<Person> FamilyMembers { get; set; }

To store Person objects, you might host the resource at a URL like http://http://www.scottseely.com/people/{Id}, where {Id} represents the ID of a given Person resource. When a web browser requests the resource, the browser uses the following HTML representation to display the Person to the user:

<html xmlns="http://http://www.w3.org/1999/xhtml" >
            <h3>Family Members:</h3>
            <p>Jean Seely</p>
            <p>Vince Seely</p>
            <p>Angie Seely</p>
            <p>Phil Seely</p>

Why did the service return HTML and how did the browser know that the representation is HTML? HTTP allows clients to request specific representations of a resource and for HTTP messages to indicate the type of data within the message through MIME types. There are MIME types for HTML (text/htmlor application/xhtml+xml), XML (text/xml or application/xml), JSON (application/json), and others. You can see a complete list of all MIME media types at http://www.iana.org/assignments/media-types/index.html. To communicate the type of resource within a message, the HTTP message includes a header named Content-Type. For example, Google’s home page indicates the content type as:

Content-Type text/html; charset=UTF-8

To request the resource using a specific format, the caller uses the HTTP Accept header, listing the MIME types in order of preference. When requesting Google’s home page as HTML, Firefox sends the following Accept string:

Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

This indicates that the browser wants the resource from http://www.google.com as a plain HTML page or as an XHTML page or as whatever the server wants to send (*/*). The q parameter indicates the preference of the MIME type on a scale of 0 to 1. When not expressed, q is set to 1.0.

Using MVC to Represent Resources

When you develop an MVC page using the standard mechanisms, you pass data between the model, view, and controller using a collection named ViewData. ViewData represents the essential information contained in the page. It is the resource being asked for. Each method that handles an inbound request populates ViewData and returns an appropriate ActionResult. If the ActionResult is a ViewResult instance, as it is when you return View() from a Controller method, the ViewData is passed to the result to be consumed and displayed. For example, when going to the home page of the MVC application, I might populate the ViewData, and hence the resource represented by the URL, with the following code:

public ActionResult Index()
    ViewData["Message"] = "Welcome to ASP.NET MVC!";
    ViewData["Person"] =
        new Person
                FirstName = "Scott",
                LastName = "Seely",

    return View();

This indicates that the resource has two values, Message and Person. Message contains the value, “Welcome to ASP.NET MVC!” Person has a value which is an object. When rendered as HTML, the two values appear with some chrome to beautify the page or to ease navigation within the site. If the content represented for consumption by some other code, we would want something other than HTML. For example, a client asking for XML should receive this:

        Welcome to ASP.NET MVC!
    <Person xmlns:i="http://http://www.w3.org/2001/XMLSchema-instance">

Likewise, a request for JSON should show:

{  "Message":"Welcome to ASP.NET MVC!",

To decide which format to show, the ActionResult returned from the Controller should look at the HTTP Accept header in the request message and format the ViewData appropriately. Instead of worrying about this for each individual message, we can create a new Controller that knows when to return HTML, XML, or JSON. Let’s call this new type AcceptTypeController. To handle its job, AcceptTypeController looks at all the Accept MIME types the client accepts and generates the right ViewResult by overriding View(string viewName, string masterName, object model). If the caller asked for JSON or XML, we return a new type, AcceptTypeResult. For HTML, we delegate to the parent class. The Controller gets access to the request Accept header through Request.AcceptTypes. The AcceptTypes array is the MIME strings listed in preferred order, so we loop through this list until we hit a MIME type we understand and return the right ViewResult instance.

protected override ViewResult View(
    string viewName, string masterName, object model)
    ViewResult retval = null;

    // Get the accept type. If it is HTML, 
    // let the base class handle the response. 
    // Otherwise, use our custom ViewResult type.
    foreach (var acceptType in Request.AcceptTypes)
        // Accept type is expressed in order of preference.
        // Make sure to allow for all known types
        if (string.Equals("application/json", acceptType,
            retval = new AcceptTypeViewResult(new
                   { ViewData = ViewData };

        if (string.Equals("application/xml", acceptType,
                          StringComparison.OrdinalIgnoreCase) ||
            string.Equals("text/xml", acceptType,
            retval = new AcceptTypeViewResult(new
                   { ViewData = ViewData };

        if (string.Equals("text/html", acceptType,
                          StringComparison.OrdinalIgnoreCase) ||
            string.Equals("application/xhtml+xml", acceptType,
            retval = base.View(viewName, masterName, model);

    // If we have nothing that matches, send back HTML.
    return retval ?? base.View(viewName, masterName, model);

By this point, the code has already decided how to handle dispatching based on the Accept header. The AcceptTypeViewResult is extremely compact. When called upon to write out the result, it delegates that responsibility to its internal DataWriter. DataWriter is yet another new type. It knows how to write out an IDictionary<string, object> using a particular MIME type.

public class AcceptTypeViewResult : ViewResult
    public AcceptTypeViewResult(DataWriter writer)
        Writer = writer;

    private DataWriter Writer { get; set; }

    public override void ExecuteResult(ControllerContext context)
        context.HttpContext.Response.ContentType = Writer.ContentType;

When writing out a dictionary, the DataWriter has three concerns:

  1. What object serializer do I use?
  2. How do I write out the dictionary tags as enclosing entities for each serialized object?
  3. What is the MIME type the DataWriter emits?

To handle this, a DataWriter derived type implements the following functions:

  1. public abstract XmlObjectSerializer CreateSerializer(Type type);
  2. public abstract void WriteStartElement(string name);
  3. public abstract void WriteEndElement(string name);
  4. public abstract string ContentType { get; }

We use XmlObjectSerializer to take advantage of the serialization work done for objects in the System.Runtime.Serialization and System.ServiceModel.Web assemblies. The assemblies contain types that do a great job reading and writing XML (DataContractSerializer) and JSON (DataContractJsonSerializer). DataWriter.WriteDictionary uses these abstractions to get the MIME type written to the HTTP response.

public void WriteDictionary(IDictionary<string, object> dictionary)
    var needSeparator = false;
    // Start the document
    foreach (var key in dictionary.Keys)
        // If this is not the first entry, emit a separator if the
        // format calls for it.
        if (needSeparator)
        needSeparator = true;
        // Check to see if we already have created the 
        // right serializer.
        var value = dictionary[key];

        if (value == null)
            // Write out the null version for the object
            // Write out the instance
            var ser = CreateSerializer(value.GetType());
            ser.WriteObject(Stream, value) ;

    // Close the document

If you are curious about the other details, I recommend that you look at the source code and try it out.


ASP.NET MVC helps developers build REST architectures for their applications. The infrastructure has enough extensibility in it to allow us to augment its behavior as needed. In this article, we looked at how we could get a current application that uses ViewData to add JSON and XML support simply by changing our custom Controller’s base class. The source code continues the idea to look at how you can also accept JSON and XML data in a request when handling HTTP PUT and POST methods.

When developing REST services for your applications, it may make sense to expose the JSON and XML functionality at the same place that you expose the HTML pages. By separating out the resource from its representation, your applications can gain quite a bit of richness without a lot of extra effort.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020