Product

Launching the Enterspeed Query API

Emil Rasmussen

CTO at Enterspeed

Thumbnail for blog post: Launching the Enterspeed Query API

Earlier this year, we launched a preview of our Query API. Since then, we’ve added new features and polished the existing ones. Today, we’re making the Query API available to every Enterspeed tenant.

I want to give a big thank you to all our early preview testers who provided invaluable feedback. Building software and prioritising improvements is not that difficult when you receive good feedback.

With the Enterspeed Query API, we enable developers to deliver a rich user experience without the need to create and maintain their own infrastructure. If you’ve been keeping a close eye on us since the preview launch, some of the following might be familiar – but don’t worry, we’ll quickly get to the new features.

How it works

The Enterspeed Query API builds upon the Enterspeed Core platform you already know. Data is sent to Enterspeed via the Ingest API, and you use the JavaScript-powered transformation engine to process it.

The two new components are:

creating an Index Schema to define your index
using the Query API to fetch the data.

The Index Schema is the behind-the-scenes magic. I recommend visiting our blog post on the topic or our documentation to learn more.

Since the preview launch, we’ve added two important features: facets and deep Delivery API integration.

Facets

Faceted search lets users filter and refine results across multiple dimensions – such as category, price, brand, or rating – making it easy to drill it down to exactly what they need. By exposing these facets in the Query API, we enable developers to create a much richer user experience.

Below is an example of a request to the Query API to get the facets.

1{
2  "facets": [
3    {
4      "field": "category"
5    }
6  ],
7  "pagination": {
8    "pageSize": 0
9  }
10}
11Response
12{
13  "totalResults": 137,
14  "results": [],
15  "facets": [
16    {
17      "name": "category",
18      "field": "category",
19      "groups": [
20        { "value": "News & Announcements", "count": 46 },
21        { "value": "Thoughts & Insights", "count": 41 },
22        { "value": "Product", "count": 25 },
23        { "value": "Guides & Tutorials", "count": 15 },
24        { "value": "Customer stories", "count": 10 }
25      ],
26      "isValid": true
27    }
28  ],
29  "status": 0
30}
31

... and here's an example of the response from the Query API returning the facets:

1{
2  "totalResults": 137,
3  "results": [],
4  "facets": [
5    {
6      "name": "category",
7      "field": "category",
8      "groups": [
9        { "value": "News & Announcements", "count": 46 },
10        { "value": "Thoughts & Insights", "count": 41 },
11        { "value": "Product", "count": 25 },
12        { "value": "Guides & Tutorials", "count": 15 },
13        { "value": "Customer stories", "count": 10 }
14      ],
15      "isValid": true
16    }
17  ],
18  "status": 0
19}
20

Delivery API integration

The Query API and the Delivery API work together by allowing the Query API to return the existing views already created in Enterspeed.

This is particularly handy when you want to create a rich user experience for finding and filtering content using a lightweight index, while still displaying a full and rich content model to the end user.

Below you can see an example of the request to have a specific view returned from the Query API. Note the aliases field in line three.

1{
2  "filters": {},
3  "aliases": [ "blogPostListItem" ],
4  "sort": [
5    { "field": "date", "order": "desc" }
6  ],
7  "pagination": {
8    "page": 0,
9    "pageSize": 1
10  }
11}
12

In line 11 below, you can see the view returned directly from the Query API.

1{
2  "totalResults": 250,
3  "results": [
4    {
5      "date": "2025-07-18T00:00:00",
6      "_originId": "9825-en-us",
7      "_updatedAt": "2025-07-18T08:21:40.8390149Z",
8      "_sourceGuid": "c008f0db-2707-4b9f-baaa-sdf23423434",
9      "category": "Product",
10      "_views": {
11        "blogPostListItem": {
12          "url": "/blog/awesome-post",
13          "title": "Build something better",
14          "date": "2025-07-18T00:00:00"
15        }
16      }
17    }
18  ],
19  "facets": [],
20  "status": 0
21}
22

Want to learn more or try it out?

If you’d like to learn more about the Query API, you can explore our documentation for Index Schemas and the Query API. You can also read our blog post on how we use the Query API ourselves.

Of course, you’re also more than welcome to reach out on any of our channels.

The Query API is enabled for every Enterspeed tenant in a limited trial version, so please do try it out.

What does it cost?

Every Enterspeed tenant includes 500 index items, so everyone can try out the Query API straight away.

To use more than 500 items in an index, you’ll need the Query API add-on. The Query API add-on costs 300 EUR per month and includes 1 index. Each additional index also costs 300 EUR per month.

Query API requests count towards your Delivery API quota. In other words, for billing purposes, the Query API is regarded as part of the Delivery API.

Reach out to us to learn more about how a plan including the Query API add-on could look for your project.