> For the complete documentation index, see [llms.txt](https://dev.ucommerce.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ucommerce.net/readme/search-and-indexing/indexing.md).

# Indexing

You will have to run a scratch index to get data into your index. There are two ways to do that - using the back office or calling the API directly, using, e.g., Postman.

{% hint style="info" %}
It is only necessary to index from scratch when importing data from external sources into Ucommerce or making a new [custom index definition](/readme/search-and-indexing/indexing/index-definitions.md#customizing-an-index-definition). When using the back office to change properties for products, etc., the back office makes sure to index the changes automatically.
{% endhint %}

{% hint style="info" %}
Only a single scratch index operation can run at any time. The API will return a *409 - Conflict* HTTP status code if a scratch index operation is already running. The back office will display the current status.
{% endhint %}

## Scratch index using the back office

Go to *Settings* -> *Search - rebuild index* -> Click *Rebuild index*

## Scratch index using the API

Send an empty `POST` request to the URL responsible for indexing:

```
https://YourStore:YourPort/ucommerce/api/v1/search
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev.ucommerce.net/readme/search-and-indexing/indexing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.