Open Data Protocol

Appearance move to sidebar hide

In computing, Open Data Protocol (OData) is an open protocol that allows the creation and consumption of queryable and interoperable Web service APIs in a standard way. Microsoft initiated OData in 2007. Versions 1.0, 2.0, and 3.0 are released under the Microsoft Open Specification Promise. Version 4.0 was standardized at OASIS, with a release in March 2014. In April 2015 OASIS submitted OData v4 and OData JSON Format v4 to ISO/IEC JTC 1 for approval as an international standard. In December 2016, ISO/IEC published OData 4.0 Core as ISO/IEC 20802-1:2016 and the OData JSON Format as ISO/IEC 20802-2:2016.

The protocol enables the creation and consumption of HTTP-based Web APIs, which allow Web clients to publish and edit resources, identified using URLs and defined in a data model, using simple HTTP messages. OData shares some similarities with JDBC and with ODBC; like ODBC, OData is not limited to relational databases.


After initial development by Microsoft, OData became a standardized protocol of the OASIS OData Technical Committee (TC).

OASIS OData Technical Committee

"The OASIS OData TC works to simplify the querying and sharing of data across disparate applications and multiple stakeholders for re-use in the enterprise, Cloud, and mobile devices. A REST-based protocol, OData builds on HTTP, AtomPub, and JSON using URIs to address and access data feed resources. It enables information to be accessed from a variety of sources including (but not limited to) relational databases, file systems, content management systems, and traditional Web sites. OData provides a way to break down data silos and increase the shared value of data by creating an ecosystem in which data consumers can interoperate with data producers in a way that is far more powerful than currently possible, enabling more applications to make sense of a broader set of data. Every producer and consumer of data that participates in this ecosystem increases its overall value."

TC participants include CA Technologies, Citrix Systems, IBM, Microsoft, Progress Software, Red Hat, SAP SE and SDL.


OData is a protocol for the creation and consumption of Web APIs. OData thus builds on HTTP, AtomPub, and JSON using URIs to address and access data feed resources.

Resource identification

OData uses URIs to identify resources. For every OData service whose service root is abbreviated as http://host/service/, the following fixed resources can be found:

The service document

The service document lists entity sets, functions, and singletons that can be retrieved. Clients can use the service document to navigate the model in a hypermedia-driven fashion.

The service document is available at http://host/service/

The metadata document

The metadata document describes the types, sets, functions and actions understood by the OData service. Clients can use the metadata document to understand how to query and interact with entities in the service.

The metadata document is available at http://host/service/$metadata.

Dynamic resources

The URIs for the dynamic resources may be computed from the hypermedia information in the service document and metadata document.

Resource operation

OData uses the HTTP verbs to indicate the operations on the resources.


URLs requested from an OData endpoint may include query options. The OData protocol specifies various 'system query options' endpoints should accept, these can be used to filter, order, map or paginate data.

Query options can be appended to a URL after a ? character and are separated by & characters; each option consists of a $-sign prefixed name and its value, separated by a = sign, for example: OData/Products?$top=2&$orderby=Name. A number of logical operators and functions are defined for use when filtering data, for example: OData/Products?$filter=Price lt 10.00 and startswith(Name,'M') requests products with a price smaller than 10 and a name starting with the letter 'M'.

Resource representation

OData uses different formats for representing data and the data model. In OData protocol version 4.0, JSON format is the standard for representing data, with the Atom format still being in committee specification stage. For representing the data model, the Common Schema Definition Language (CSDL) is used, which defines an XML representation of the entity data model exposed by OData services.

A sample OData JSON data payload

A collection of products:

{ "@odata.context": "$metadata#Products", "value": } A sample OData Atom data payload

A collection of products:

<feed xml:base="" m:context="$metadata#Products" xmlns="" xmlns:d="" xmlns:m="" xmlns:georss="" xmlns:gml=""> <id></id> <title type="text">Products</title> <updated>2015-05-19T03:38:50Z</updated> <link rel="self" title="Products" href="Products"/> <entry> <id></id> <category term="#ODataDemo.Product" scheme=""/> <link rel="edit" title="Product" href="Products(0)"/> <link rel="" type="application/xml" title="Categories" href="Products(0)/Categories/$ref"/> <link rel="" type="application/atom+xml;type=feed" title="Categories" href="Products(0)/Categories"/> <link rel="" type="application/xml" title="Supplier" href="Products(0)/Supplier/$ref"/> <link rel="" type="application/atom+xml;type=entry" title="Supplier" href="Products(0)/Supplier"/> <link rel="" type="application/xml" title="ProductDetail" href="Products(0)/ProductDetail/$ref"/> <link rel="" type="application/atom+xml;type=entry" title="ProductDetail" href="Products(0)/ProductDetail"/> <title/> <updated>2015-05-19T03:38:50Z</updated> <author> <name/> </author> <content type="application/xml"> <m:properties> <d:ID m:type="Int32">0</d:ID> <d:Name>Bread</d:Name> <d:Description>Whole grain bread</d:Description> <d:ReleaseDate m:type="DateTimeOffset">1992-01-01T00:00:00Z</d:ReleaseDate> <d:DiscontinuedDate m:null="true"/> <d:Rating m:type="Int16">4</d:Rating> <d:Price m:type="Double">2.5</d:Price> </m:properties> </content> </entry> <entry> <id></id> <category term="#ODataDemo.Product" scheme=""/> <link rel="edit" title="Product" href="Products(1)"/> <link rel="" type="application/xml" title="Categories" href="Products(1)/Categories/$ref"/> <link rel="" type="application/atom+xml;type=feed" title="Categories" href="Products(1)/Categories"/> <link rel="" type="application/xml" title="Supplier" href="Products(1)/Supplier/$ref"/> <link rel="" type="application/atom+xml;type=entry" title="Supplier" href="Products(1)/Supplier"/> <link rel="" type="application/xml" title="ProductDetail" href="Products(1)/ProductDetail/$ref"/> <link rel="" type="application/atom+xml;type=entry" title="ProductDetail" href="Products(1)/ProductDetail"/> <title/> <updated>2015-05-19T03:38:50Z</updated> <author> <name/> </author> <content type="application/xml"> <m:properties> <d:ID m:type="Int32">1</d:ID> <d:Name>Milk</d:Name> <d:Description>Low fat milk</d:Description> <d:ReleaseDate m:type="DateTimeOffset">1995-10-01T00:00:00Z</d:ReleaseDate> <d:DiscontinuedDate m:null="true"/> <d:Rating m:type="Int16">3</d:Rating> <d:Price m:type="Double">3.5</d:Price> </m:properties> </content> </entry> ... </feed> A sample OData metadata document <edmx:Edmx Version="4.0" xmlns:edmx=""> <edmx:DataServices> <Schema Namespace="ODataDemo" xmlns=""> <EntityType Name="Product"> <Key> <PropertyRef Name="ID"/> </Key> <Property Name="ID" Type="Edm.Int32" Nullable="false"/> <Property Name="Name" Type="Edm.String"/> <Property Name="Description" Type="Edm.String"/> <Property Name="ReleaseDate" Type="Edm.DateTimeOffset" Nullable="false"/> <Property Name="DiscontinuedDate" Type="Edm.DateTimeOffset"/> <Property Name="Rating" Type="Edm.Int16" Nullable="false"/> <Property Name="Price" Type="Edm.Double" Nullable="false"/> </EntityType> <ComplexType Name="Address"> <Property Name="Street" Type="Edm.String"/> <Property Name="City" Type="Edm.String"/> <Property Name="State" Type="Edm.String"/> <Property Name="ZipCode" Type="Edm.String"/> <Property Name="Country" Type="Edm.String"/> </ComplexType> <EntityContainer Name="DemoService"> <EntitySet Name="Products" EntityType="ODataDemo.Product"></EntitySet> </EntityContainer> </Schema> </edmx:DataServices> </edmx:Edmx>


The ecosystem of OData consists of the client/server libraries that implement the protocol, and applications that are based on the protocol.


There are a number of OData libraries available to access/produce OData APIs:

.NET Java JavaScript PHP Python Ruby Others

Other languages implemented include:


Applications include:


See also


  1. ^ Flasko, Mike (18 July 2007). "Welcome!". MSDN Blogs. OData Team. Archived from the original on May 5, 2014.
  2. ^ "OASIS Open Data Protocol (OData) Technical Committee". Retrieved 2013-08-05.
  3. ^ "OASIS Approves OData 4.0 Standards for an Open, Programmable Web". 17 March 2014.
  4. ^ "OASIS has Submitted OData v4 and OData JSON Format v4 to ISO/IEC JTC 1 for approval as an International Standard". MS Open Tech. Archived from the original on 2015-05-20. Retrieved 2015-05-18.
  5. ^ "OData Published as an ISO Standard · OData - the Best Way to REST". Retrieved 2021-05-11.
  6. ^ "ISO/IEC 20802-1:2016". ISO. Retrieved 2021-05-11.
  7. ^ "ISO/IEC 20802-2:2016". ISO. Retrieved 2021-05-11.
  8. ^ "OASIS Open Data Protocol (OData) TC | OASIS". Retrieved September 24, 2019.
  9. ^ Microsoft's OData .NET libraries
  10. ^ Simple.OData.Client
  11. ^ Apache Olingo
  12. ^ Jello-Framework
  13. ^ odata-client
  14. ^ Apache Olingo
  15. ^ "Libraries · OData - the Best Way to REST". Retrieved 2019-02-19.
  16. ^ "data.js". CodePlex Archive.
  17. ^ JayData
  18. ^ JayData for node
  19. ^ Breeze
  20. ^ OData4 and Invantive Bridge Online
  21. ^ odata-fluent-query
  22. ^ node-odata
  23. ^ odataphp
  24. ^ POData
  25. ^ PyOData
  26. ^ Pyslet
  27. ^ ruby_odata library
  28. ^ Free OData V4.0 Library for Ruby
  29. ^ Safrano
  30. ^ "Libraries".
  31. ^ ASP.NET Ajax Library
  32. ^ odatacpp_client
  33. ^ Windward Studios
  34. ^ OData-BB10
  35. ^ "Ecosystem".
  36. ^ Progress DataDirect Hybrid Data Pipeline
  37. ^ "SAP NetWeaver Gateway". Retrieved 2012-11-22.
  38. ^ IBM developerWorks eXtreme Scale REST data service (OData)
  39. ^ "Welcome to Office 365 APIs". 28 August 2018. Retrieved September 24, 2019.
  40. ^ "Set Up Salesforce Connect to Access External Data with the OData 2.0 or 4.0 Adapter".
  41. ^ Skyvia Connect
  42. ^ "OData - Tableau". Retrieved September 24, 2019.
  43. ^ "OData and Spotfire". The TIBCO Blog. Retrieved 2016-03-30.
  44. ^ Mulesoft
  45. ^ "Anypoint Exchange". Retrieved September 24, 2019.
  46. ^ SuccessFactors
  47. ^ Ceridian HCM's Dayforce
  48. ^ "HR Reporting Software - Dayforce | Ceridian". Retrieved September 24, 2019.
  49. ^ "What You Need to Know About Redfish API". Exxact. 2017-12-01. Retrieved 2019-08-31.
  50. ^ "Nucleon Database Master". Retrieved 16 November 2017.

OData OASIS Standards

Committee Specifications

Committee Notes