> 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/optional-interfaces/changing-deleting-and-adding-records-delta-updates.md). # Changing, deleting and adding records (delta updates) Apply incremental record changes with delta updates and understand when to use them safely. This interface lets you update, delete, or add individual records or batches of records in the search database. > Changes made through this interface may be overwritten by the next data import. The product data export from your shop system remains the basis for imports. Use this interface mainly for temporary fixes or quick record corrections. Changes are available in search immediately. When you save the database, the changes are written to disk and remain available after a restart. Saving requires processing power, so it should not be done after every single change request. ### REST-Interface The REST API documentation is part of the search application and is available at \[your NG server]/fact-finder/swagger-ui.html. You can also access it here: Swagger Link: The relevant methods are documented under `records`. In addition to parameter documentation, you can test requests and inspect the results directly. Because the documentation is built with Swagger, you can also use Swagger Codegen to generate a client for your code. > Important: > > * Only send actual data changes to FactFinder. > * Queue updates and send multiple changes in one request whenever possible. > * Use delta updates for incremental changes, and keep a regular daily `csv` import as your baseline. --- # 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/integration/factfinder-search-integration/optional-interfaces/changing-deleting-and-adding-records-delta-updates.md?ask=&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.