[IMPLEMENTED] Web API - which type of document type

  • [ ] Regression (a behavior that stopped working in a new release)

  • [ ] Bug report

  • [ ] Performance issue

  • [ X] Documentation issue or request

  • [ ] Self hosted with docker

  • [X ] Self hosted with IIS

  • [ ] Self hosted with other version

  • [ ] Cloud version

Version: 3.5

The new multi reference types are great.

However, the document types are not given in the Web API.

How can I find out which ID belongs to which document type?

We use the Squidex.ClientLibrary Nuget.

There is no field yet, but each content has links, which could be used.

"_links": {
                "self": {
                    "href": "/api/content/squidex-website/blog/3e2e99a1-4132-4ef9-857b-473991fe0050",
                    "method": "GET"
                },

And I can also add a field.

ok. aber wie geht das genau?

Ich habe folgende Situation:
Model:

 public class PageData
    {
        public Dictionary<string, string> Title { get; set; }
        
        public Dictionary<string, string> Slug { get; set; }
        
        [JsonConverter(typeof(InvariantConverter))]
        public string[] Content { get; set; }

        public Dictionary<string, string> MetaKeywords { get; set; }

        public Dictionary<string, string> MetaDescription { get; set; }
    }

Call:

public async Task<Page> GetAsync(string slug, string lang = "de")
        {
            var filter = $"data/slug/de eq '{slug}'";
            var data = await _clientManager
                .GetClient<Page, PageData>("page")
                .GetAsync(new ODataQuery { Filter = filter });

            return data.Items.FirstOrDefault();
        }

The Content field returns all IDs.
Do I have to use OData for linking?

or how can I use the linking?

Sorry, I think I’m standing on the hose.

I have to make a few modifications to the client library. I hope I can do it this evening.

that would be great :slight_smile:

Hi, a new build is on its way which provides the app name and schema name for each content item and also an endpoint to query contents by its ids only:

Ok i look.

Thx a lot :slight_smile:

Have you had a chance to check out the newest version?