Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Query REST Data Using the OData SDK for PHP
You can use the API Server and the OData PHP SDK to easily consume REST entities in PHP by modeling them as objects.
The CData API Server, when paired with the ADO.NET Provider for REST, exposes REST data (or data from any of 200+ other ADO.NET Providers) as Web services. You can follow the procedure below to work with REST data as PHP objects.
Set Up the API Server
Follow the steps below to begin producing secure REST OData services:
Deploy
The API Server runs on your own server. On Windows, you can deploy using the stand-alone server or IIS. On a Java servlet container, drop in the API Server WAR file. See the help documentation for more information and how-tos.
The API Server is also easy to deploy on Microsoft Azure, Amazon EC2, and Heroku.
Connect to REST
After you deploy the API Server and the ADO.NET Provider for REST, provide authentication values and other connection properties needed to connect to REST by clicking Settings -> Connections and adding a new connection in the API Server administration console.
See the Getting Started chapter in the data provider documentation to authenticate to your data source: The data provider models REST APIs as bidirectional database tables and XML/JSON files as read-only views (local files, files stored on popular cloud services, and FTP servers). The major authentication schemes are supported, including HTTP Basic, Digest, NTLM, OAuth, and FTP. See the Getting Started chapter in the data provider documentation for authentication guides.
After setting the URI and providing any authentication values, set Format to "XML" or "JSON" and set DataModel to more closely match the data representation to the structure of your data.
The DataModel property is the controlling property over how your data is represented into tables and toggles the following basic configurations.
- Document (default): Model a top-level, document view of your REST data. The data provider returns nested elements as aggregates of data.
- FlattenedDocuments: Implicitly join nested documents and their parents into a single table.
- Relational: Return individual, related tables from hierarchical data. The tables contain a primary key and a foreign key that links to the parent document.
See the Modeling REST Data chapter for more information on configuring the relational representation. You will also find the sample data used in the following examples. The data includes entries for people, the cars they own, and various maintenance services performed on those cars.
You can then choose the REST entities you want to allow the API Server access to by clicking Settings -> Resources.
Additionally, configure the API Server for compatibility with the OData SDK for PHP: Click Server -> Settings and in the OData section set Default Version to 2.0.
Authorize API Server Users
After determining the OData services you want to produce, authorize users by clicking Settings -> Users. The API Server uses authtoken-based authentication and supports the major authentication schemes. You can authenticate as well as encrypt connections with SSL. Access can also be restricted based on IP address; by default, only connections from the local machine are allowed.
For simplicity, we will authenticate to the API Server by setting the authtoken in the URL. This is not enabled by default; you will need to add the following lines to the API Server configuration file, settings.cfg.
[Application]
AllowAuthTokenInUrl = true
The settings.cfg file is located in the data directory. In the .NET edition, the data directory is the app_data folder under the www folder. In the Java edition, the data directory's location depends on the operation system:
- Windows: C:\ProgramData\CData\REST\
- Unix or Mac OS X: ~/cdata/REST/
Work with REST Entities as PHP Objects
Follow the steps below to use the ODataPHP SDK to create a proxy class that will connect to the Web services exposed by the API Server.
-
Pass the URL to a command like the one below:
php C:\PHPLib\ODataphp\PHPDataSvcUtil.php /uri=https://your-server:8032/api.rsc/@your-authtoken/ /out=C:\PHPLib\ODataphp\RESTEntities.php
The preceding command defines classes from the metadata returned in the response from the OData endpoint, then outputs the class definitions to the specified folder.
Both the API Server and the OData SDK for PHP support forms and Windows authentication. The API Server uses authtokens to authenticate users authorized to access the OData endpoint. You can supply authtokens in HTTP Basic authentication or append them to the OData URL.
You can configure authorized users in the Settings -> Users section of the API Server administration console.
-
You can now start accessing REST data using an object-oriented interface in PHP. The code below creates a record of the people table and then retrieves the live data, showing the newly created record.
require_once 'RESTEntities.php'; try{ $svc = new CData(); $people = new people(); $people->[ personal.name.last ] = 'Roberts'; $svc->AddTopeople($people); $svc->SetSaveChangesOptions(SaveChangesOptions::None); $svc->SaveChanges(); $response = $svc->people()->Execute(); foreach($response->Result as $people) echo $people->[ personal.name.first ].""; } catch (Exception $e) { //catch errors from the API Server echo $e->getError(), "\n"; }