> 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/webcomponents-overview/api/core-api/request-pipelines.md).
# Request Pipelines
This page provides various pipeline diagrams that visualize data flow and events as they occur during the lifecycle of a request.
You can see how the options you provide to a request influence the pipeline.
At various stations you will find references to relevant API and pipeline control parameters from e.g. *RequestOptions*.
If a reference's location in the API is unclear, go look it up in [Type Definitions](/webcomponents-overview/api/core-api/type-definitions.md) or [API Overview](/webcomponents-overview/api/core-api/api-overview.md).
{% hint style="info" %}
**Study well**
Afford plenty of time to study these diagrams. They will give you a thorough understanding of how the Web Components library behaves given the many available options.
This page is likely going to be your best companion during development. You might want to keep it open at all times.
{% endhint %}
## Legend
This is the legend of the elements that appear in the various pipeline diagrams.
## Search
This diagram applies to requests from the `factfinder.request` namespace.
It is likely the one you will be using the most.
## Suggest
This pipeline is invoked when an `ff-suggest-item` element of the [Suggest](/webcomponents-overview/api/basic-elements/suggest.md) component is clicked **before** it typically invokes either a *Search* or a *Navigation* request.
## Tracking
The tracking pipeline is basically identical to the *Search* pipeline except that it has no response pipeline other than success and fail handlers.
It applies to requests from the `factfinder.tracking` namespace.
---
# 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/webcomponents-overview/api/core-api/request-pipelines.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.
