> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/infinity/developer-guide/syncing.md).

# Syncing

### Syncing

Infinity needs an up to date description of your product catalog in order to provide correct results. Have a look at the [product feed guide](https://docs.fact-finder.com/infinity/developer-guide/the-product-feed.md) for more details on how to export the product catalog. After the initial data import Infinity needs to be continuously updated by regularly syncing the feed. This sync will be scheduled to run at regular time intervalls by your Infinity Customer Success Manager. In addition to the scheduled syncs you can also trigger a sync job by calling the API.

### Sync Call

* [C#](#tabs-1)
* [JAVA](#tabs-2)
* [JAVASCRIPT](#tabs-3)
* [PHP](#tabs-4)

```
//create a client with a null client info provider (because we don't need user context when syncing)
IInfinityClient client = new InfinityClient(new RequestManager(new InfinitySettings("https://helloworld.54proxy.com", "TestApiKey")),
    new NullClientInfoProvider());

Response response = client.Sync();
```

The `sync()` call is also available [via the API.](https://docs.loop54.com/api/docs.html#tag/Administrative/paths/~1sync/post)

C# source code on Github: [SyncController.cs](https://github.com/LoopFiftyFour/.NET-Connector/blob/master/Loop54.NetCoreCodeExamples/Controllers/SyncController.cs)

```
// Set up a InfinityClient with an Api key and a null client info (we don't need metadata about the user here)
InfinitySettings settings = new InfinitySettings("https://helloworld.54proxy.com", "TestApiKey");
IInfinityClient client = new InfinityClient(new RequestManager(settings), () -> new NullClientInfo());

Response response = client.sync();
```

The `sync()` call is also available [via the API.](https://docs.loop54.com/api/docs.html#tag/Administrative/paths/~1sync/post)

C# source code on Github: [SyncController.java](https://github.com/LoopFiftyFour/Java-Connector/blob/master/codeexamples/src/main/java/com/loop54/spring/test/codeexamples/web/SyncController.java)

```
var client = Infinity.getClient("http://helloworld.54proxy.com", null, "TestApiKey");
var response = client.sync();
```

The `sync()` call is also available [via the API](https://docs.loop54.com/api/docs.html#tag/Administrative/paths/~1sync/post).

C# source code on Github: [Sync.js](https://github.com/LoopFiftyFour/JS-Connector/blob/master/codeexamples/sync.js)

```
var client = Infinity.getClient("http://helloworld.54proxy.com", null, "TestApiKey");
var response = client.sync();
```

The `sync()` call is also available [via the API.](https://docs.loop54.com/api/docs.html#tag/Administrative/paths/~1sync/post)

C# source code on Github: [Simple.php](https://github.com/LoopFiftyFour/PHP-Connector/blob/master/examples/Simple.php)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fact-finder.com/infinity/developer-guide/syncing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
