Sitefinity CMS exposes it's data via oData services. As in the oData flow, Sitefinity CMS allows the registration of one or more routes to handle client requests.
The URL of the web service is composed from the URL of the route and the URL of the service.
EXAMPLE: Each available resource can be found via the following URL convention: <www.yoursite.com>/<RouteUrlName>/<ServiceUrlName>/<TypeUrlName>
Sitefinity CMS has the concept of a default route. The backend UI for service exposure depends on this property, because it allows the management of the services for a single selected route.
By default, Sitefinity CMS has a single route installed under the /api URL. You can change the URL name of the route, if it conflicts with any existing APIs.
IMPORTANT: When making requests to the service include the following header in the request: X-SF-Service-Request: true.
It is needed to successfully call protected services and not receive 401(Unauthorized)
Each route has a UrlName property and a Name property. The UrlName of the route is the first segment in the URL that is used to build up the full URL.
NOTE: UrlName property must be unique and does not allow special characters or multiple segments.
You can change the URL of the service when you create or edit it. You can change the URL of the route in the Advanced setting of the web services module.
To change the name or the URL of the route, perform the following:
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity