Product: Sitecore Services Client

How can we improve Sitecore Services Client?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Expose Sitecore.Services as standalone NuGet package

    Currently Sitecore.Services.Client is delivered as a standard Sitecore Zip package and takes a dependency on Sitecore.Kernel.dll.

    It would be useful to some consumers of the service layer if Sitecore.Services could be separated out as a distinct NuGet package that contains no Sitecore specific dependencies.

    13 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

    • 9 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)

        We’ll send you updates on this idea

      • Create a C# HTTP client wrapper for Sitecore Services Client

        Create a C# HTTP client for Sitecore Services Client with async HTTP client support

        9 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)

          We’ll send you updates on this idea

        • Async support in Entity Services

          Entity Services have no dependency on Sitecore APIs and for 100% external data they can (and arguably should) be async

          8 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)

            We’ll send you updates on this idea

          • 7 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)

              We’ll send you updates on this idea

            • Ability to move endpoint away from /sitecore URL

              SSC is available at /sitecore/api/... What if I want to disable /sitecore/* on my CD alltogether and block it on the firewall or have a global URL rewrite rule? Or maybe I just don't want the details of what the web site / app is built on to be "visible"? Whatever the case might be - would be nice if I could re-map the SSC endpoints to go somewhere else. Maybe I can do this with the handler configuration. Then at least a chapter in the documentation / scaling guide would be nice :)

              5 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)

                We’ll send you updates on this idea

                1 comment  ·  Admin →
              • Root request to /sitecore/api/ssc/ should list service controller locations

                # SSC API Root [/sitecore/services]

                This resource does not have any attributes. Instead it offers the initial API affordances in the form of the links in the JSON body.

                It is recommend to follow the “url” link values,
                [Link](https://tools.ietf.org/html/rfc5988) or Location headers where
                applicable to retrieve resources. Instead of constructing your own URLs, to keep your client decoupled from implementation details.

                ## Retrieve the Entry Point [GET]

                + Response 200 (application/json)

                {
                "Sitecore.FXM.Service.Controllers.ElementMatcher": "/sitecore/api/ssc/elementmatcher/service",

                ...
                }

                4 votes
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                • Simpler JS wrapper

                  I mostly use SSC outside of SPEAK context (I in general am not a big fan of SPEAK but I will save that for another uservoic ebut in short - way too many ceremonies and way to much configuration over convention and way to many moving parts). And outside of SPEAK my databinidng needs are often different. Basically we mostly go after the raw JSON by talking to the endpoint URL directly bypassing any JS wrappers that come with SSC. I think some lightweight wrapper that doesn't objectifies the raw response would be a nice addition

                  2 votes
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                  • Configurable behavior for Location header in response to Add()

                    I need to dig into the details of this one but I noticed something interesting/weird recently. The base Add() on a repository responds back with 201 and a Location header pointing to GetAll() (or what its name). I sae Firefox actually going after the URL in the Location header and reporting an error in the console about not an object literal coming back (what comes back is an array literal). While 201 + Location may be the correct REST semantics I don't sure the browser asking for what's in Location in the backgound is correct. Maybe it can be made…

                    1 vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                    • Don't see your idea?

                    Product: Sitecore Services Client

                    Feedback and Knowledge Base