Skip to the content
Documentation

restrest

Extending the REST API   The Exponential 5 REST API comes with a framework that makes it quite easy to extend the API for your own needs. While most of what can be found here w... Making cross-origin HTTP requests Exponential ships with NelmioCorsBundle, a Symfony open-source bundle that provides support for CORS (Cross Origin Resource Sharing). The REST API is pre-configured to respond to such requests, as long as you customize the allowed origins as explained below. Making cross-origin HTTP requests (page id 31430329) Exponential ships with NelmioCorsBundle, a Symfony open-source bundle that provides support for CORS (Cross Origin Resource Sharing). The REST API is pre-configured to respond to such requests, as long as you customize the allowed origins as explained below. REST API Countries list (page id 31430297) Countries list is a REST service that gives access to an ISO-3166 formatted list of world countries. It is useful when presenting a country options list from any application. General REST usage (page id 31430291) As explained in the introduction, the REST API is based on a very limited list of general principles: REST API Authentication (page id 31430293) The REST API supports two authentication methods: session, and basic. Getting started with the REST API (page id 31430289) No special preparations are necessary to use the REST API. As long as your eZ Platform is correctly configured, the REST API is available on your site using the URI /api/ezp/v2/. If you have installed eZ Platform in a subfolder, prepend the path with this subfolder: http://example.com/sub/folder/exp REST API reference (page id 31430594) The complete reference (specification) of the REST API resources is found bundled with your software, or online: Error handling (page id 31430302) Error handling in the REST API is fully based on HTTP error codes. As a web developer, you are probably familiar with the most common ones: 401 Unauthorized, 404 Not Found or 500 Internal Server Error. The REST API uses those, along with a few more, to allow proper error handling. Error handling Error handling in the REST API is fully based on HTTP error codes. As a web developer, you are probably familiar with the most common ones: 401 Unauthorized, 404 Not Found or 500 Internal Server Error. The REST API uses those, along with a few more, to allow proper error handling.