The page endpoint is the heart of the Makaira Marketing Suite when it comes to using Enterprise features like the page editor.
It's main purpose is retrieving a page document for a given URL.
In the most simple case, the URL belongs to Landingpage that was created in the Makiara-Backend. In this case, it is enough to supply the URL and Shop-ID in the request body.
In more advanced cases, the URL may belong to a category or manufacturer page. In this case, you can and should supply additional information in the request body, e.g. for sorting or pagination.
Resolves a URL to its corresponding page editor page or search results. This is the primary endpoint for storefront routing — the storefront sends the current URL and receives back the page content or search results.
Request
POST /enterprise/page
Headers
| Header | Value |
|---|---|
Content-Type | application/json |
X-Makaira-Instance | Your Makaira instance identifier |
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
url | string | Yes | The URL path to resolve (e.g. /men/shoes). |
constraints | object | Yes | Must include query.shop_id and query.language. |
isSearch | boolean | No | Set to true if the URL represents a search results page. |
searchPhrase | string | No | Search phrase for search result pages. |
enableAggregations | boolean | No | Include filter aggregations in the response. |
aggregations | object | No | Active filter selections. |
sorting | object | No | Sorting configuration. |
count | integer | No | Number of products per page. |
offset | integer | No | Pagination offset. |
Example Request
{
"url": "/men/shoes",
"constraints": {
"query.shop_id": "1",
"query.language": "de"
},
"isSearch": false,
"enableAggregations": true,
"aggregations": [],
"sorting": [],
"count": 24,
"offset": 0
}Response
Returns the resolved page content including product results, page components, and metadata.
OK