> 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/integration/factfinder-search-integration/integrating-the-search-into-the-shop-system/integration-via-api-rest.md).

# Integration via API (REST)

The following diagram shows API-based integration at a high level:

![](/files/cKSLor8DgMIXV9m5XKHR)

## Preparations and design

The server-side integration layer sits between the FactFinder Search server and your shop pages. It handles communication between the two systems. Build this layer before you start the API integration.

The steps are as follows:

1. Send the search query to FactFinder. The search parameters entered by the user must be sent to the FactFinder Search server through an HTTP request.
2. Receive the search results. The FactFinder Search server returns the results in a structured response such as XML or JSON.
3. Process the search results. Your shop system must parse the returned data.
4. Render the search results page. The page structure should be based on the returned search result data.

The main difference from a Web Components integration is that your shop renders the search results page itself. This keeps the design in one place and makes it easier to maintain.

## Ways to integrate

The integration via API comes in two flavors:

1. Develop the integration code from scratch. All required information is available in your Swagger UI at `https://[your FactFinder setup here]/FactFinder/swagger-ui.html`. You can also find demos and examples on [GitHub](https://github.com/fact-finder).
2. Use **Swagger Codegen**. It generates classes such as `SearchRequest`, `SearchParams`, and `TrackingApi` automatically, which simplifies your integration code. Learn more in [How to use Swagger Codegen for the integration via API](/integration/factfinder-search-integration/integrating-the-search-into-the-shop-system/how-to-use-swagger-codegen-for-the-integration-via-api.md).


---

# 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://docs.fact-finder.com/integration/factfinder-search-integration/integrating-the-search-into-the-shop-system/integration-via-api-rest.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.