I am in the process of adapting my web app which uses the OData endpoints of Tridion 2013 to use the new endpoints offered by SDL Web 8.

My old app used these two URLs to access the Tridion 2013 linking and content services respectively

I am able to retrieve content from the SDL Web 8 server using the following URL

I am now trying to figure out the URL for the new Content Service Linking API which is documented here. The specific extract that has me confused is this:

The linking commands are exposed under the URL /linking.svc/ relative to the root of the Content Service.

Does this mean my linking service will be at this URL?

When I try to use that, I get the following error:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
    <message xml:lang="en-US">Property 'linking' cannot be requested, there was no resource selected</message>

Any suggestions for what this URL should be would be greatly appreciated, or what I might be doing wrong.


1 Answer 1


Linking service is moved to root of the content service. You can access it like


For example to get Component link

  • you are my hero. I guess this is a documentation defect as the docs imply that you should use the ".svc" extension. I will add it to the doc portal. Commented Jul 5, 2016 at 12:37
  • Also dynamic Link can work like this - localhost:8081/linking/… which should return HTM link text "DynamicLink". Source will have resolved url to link to the TargetComponentUri. Commented Feb 6, 2019 at 6:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.