You can now read Delivery views as your own C# types. Keep the flexible fetch you know, but de-serialise per-view into real models with IntelliSense and compile-time safety. No more rummaging through dictionaries.

What’s new

• Typed variant of Fetch: fetch as usual, then read each view with GetContent().
• Per-view typing: mix multiple handles (e.g. article, navigation, footer) in one request and deserialise each into its own model.

Why it matters

• Fewer runtime surprises: let the compiler and your IDE do the heavy lifting.
• Cleaner contracts: define a C# model instead of magic dictionary keys all over your code base.
• Less boilerplate: no need for custom serialization.

Example: multiple views, multiple types

Fetch several views in one go, then read each as its own model:

Useful links

• Delivery SDK (.NET) repo & README – install, register, usage, and strongly-typed examples. GitHub
• Docs: Delivering data – overview of Delivery API. Enterspeed Documentation | Enterspeed Docs

Thanks to the community

This shipped because a user opened a clear feature request with suggested behaviour. So, keep the issues and PRs coming – we’re listening.

We’ve improved how you track deployments in the Activity section. Instead of just seeing that “someone deployed something,” you now get full transparency:

• Clear logs showing deployments – including who did it
• Optional comments attached to each deployment, so you can understand the why
• See which items were deployed together
• Detailed history for individual schemas, including when they were created or published

These improvements make it easier to keep track of projects and give you a complete overview of who did what, when, and why.

Go to your activity log to see what you can do: https://app.enterspeed.com/settings/activity-logs

We are proud to announce the public release of our new Query API, adding even more power to the Enterspeed platform.

The last couple of months during the public preview phase we've gained a lot of valuable feedback and brought a lot of this feedback into the public release. Thank you so much to all of you helping to shape and make Enterspeed an even better product.

The Enterspeed Query API

The Enterspeed Query API lets you easily build search indexes from a new Index schema type and return lists of items – directly within the Enterspeed platform. It also, as the name implies, brings a new Query API that lives side by side with the existing Delivery API, which gives you even more power and flexibility in the way you can fetch data from Enterspeed.

Some of the highlights in the Query API are:

• Easy creation of new search indexes without new infrastructure or external search providers
• Filtering, sorting, pagination, and even facets on request time
• Deep integration with existing full-schema views, letting the query result return views
• Do multiple queries in a single request

Quick start

1. Create an Index Schema for the data you need list/filter on (e.g., productIndex). Index schemas define the fields and their types you want in the index and maps the data to go into the index.
2. Get an Environment API key (Management App → Environment client) to call Delivery & Query API. Just like you know it from the Delivery API.
3. Query the index via POST https://query.enterspeed.com/v1/{indexAlias} with filters/sort/pagination — optionally add aliases to get Delivery API views per item. 

Check out the full launch blog (background, facets & Delivery API integration examples - plus pricing) 👉 Launching the Enterspeed Query API 

Links

• Query API docs (endpoint, filters, facets, aliases, responses) Enterspeed Docs
• Index Schemas (when & why to use indexes vs. full schemas) Enterspeed Docs

Fetching data from Enterspeed has just become 100 times easier. With the new Query API, you can create dynamic queries on the data you have in Enterspeed. This means you can now effortlessly create product list pages, article lists, or any other type of list you need. Additionally, you can look up specific customers' orders or events within specific date ranges and locations.

The Query API introduces several new concepts, including the Index Schema, which allows you to define and manage searchable properties, and the Query API Endpoint, a new endpoint in the Enterspeed ecosystem: query.enterspeed.com.

In the Index Schema, you create and manage dynamic queries on your data.

The Query API supports filtering and sorting, and pagination. For instance, you can filter on fields defined in the Index Schema with various operators like equals and greaterThan.

For more detail, please jump to the product article 👉 The Enterspeed Query API is in preview 

What’s next?

• Properties method: Currently, the PropertiesContext object is not available, but we are working on reintroducing this functionality.
• Facets support: We are also working on bringing support for facets to the Query API, expected before summer.

How to get started

To learn more about the Query API, visit our documentation. 

If you want to try out this feature, please reach out to us, and we’ll activate the feature and give you a 1:1 introduction.

We are thrilled to see how you will use the Query API to enhance your projects!

You can now get an e-mail notification whenever Enterspeed creates, updates, or resolves an incident on any of our services including:

• Delivery API
• Ingest API
• Management App API
• enterspeed.com

By subscribing, you’ll receive status notifications directly if there are any changes to our system's performance and we’ll also use the updates to announce any planned maintenance windows.

Simply jump to Enterspeed status and subscribe to get the latest updates delivered straight to your inbox.

Have you ever wanted to know what a view response looks like from the Delivery API – or maybe wanted to see resolved references for a view? Good news! You can now do that directly from the Generated views panel in the Management App.

In addition to copying a CURL request from the routes list, you can now execute the request directly and view the response from the Delivery API within the app. This feature is particularly useful for seeing the full view, including resolved references, as shown in the examples below.

The statically generated view holds a single unresolved reference for a productListingView. This is how the view is stored as references are resolving during the Delivery API request.

When you execute the CURL request against the Delivery API, you can now see the full response, including the resolve productListingView reference.

We've also introduced the ability to make CURL requests by id. In the Enterspeed Delivery API, you can fetch a view in three ways: by URL, by handle, or by id. URLs and handles are routes you create using the routes function in a schema. Previously, we only provided CURL options for these explicit routes. Now, we've added the id CURL request, allowing you to fetch views without relying on explicit routes. This makes it easier to test references for these views. 

If you’re (also) one of those people who enjoy insights and transparency in your services, you’re gonna like the Ingest requests tile on the dashboard that we’ve just introduced.

The new tile displays the current month’s number of ingest request. You’ll see both the total number of ingest requests and the number of changed ingest requests. These two numbers provide a change ratio, which indicates the percentage of total ingest requests that have changed.

We hope the new tile can help you understand and optimise your integrations to Enterspeed.

Besides the ingest numbers, the new Ingest requests tile is the first tile on the dashboard where you can configure different view options for the tile. We hope to bring this concept to some of the existing tiles as well in the future.

The Versions page in the Enterspeed Management app have gotten an update. And we think you will like it 😀

Check out the features below.

Performance improvements
The page now loads faster, especially if you have many environments.

New version indication
A red dot on the version number is indicating if a newer version exists.

Deployment status
When a schema is actively being deployed, an animation will show the transition from the current version number to the new version number. As soon as the deployment is completed the version number is updated.

The new deployment indicator on the Versions page is just the first step on the way to give your more insights to the status of schema deployments.

Umbraco 15 is out – and as always, we have upgraded our integration to support the new Umbraco version 👌

Besides the support of Umbraco 15, the new package also contains some new features and fixes, like support for the new RTE editor and the option to remove trailing slashes in the URLs. 

So, make sure to check out the Enterspeed package on Umbraco marketplace.

OBS, if you are using Umbraco 9 to 15, make sure to get the right package version 😉

Version 5.x is for Umbraco version is 14 or higher.
Version 4.x is for Umbraco version 9 to 13.

We’ve made a small but significant update to the Tenant Health tile. Back in warm and sunny August, we introduced the Tenant Health tile to the Overview section of the Enterspeed app home page. This tile provides a quick overview of recent errors in your transformations. However, as we received more and more questions about errors that seemingly didn’t affect anything, we realised there was room for improvement.

Upon reviewing the errors reported in the Tenant Health tile and Logs, we realised that some of the errors weren’t actually errors. When one of the millions of view generations in Enterspeed each month fails, the system automatically retries the failed job. Previously, each failed attempt was logged as an error, even if the job was retried and successfully completed moments later.

With this update, errors that are successfully retried will no longer appear in the Tenant Health tile. We apologise for any unnecessary alarm caused in the past — rest assured, move along, nothing to see here 🙆‍♀️