> For the complete documentation index, see [llms.txt](https://docs.transparentedge.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.transparentedge.eu/getting-started/dashboard/prefetch.md).

# Prefetching Cache

With **Prefetching cache**, you tell Transparent Edge which content to load into the cache of every edge node *before* your visitors ask for it. This is known as *warming up* the cache: when the first visitor arrives, the content is already there, so they get the fast response instead of waiting for it to be fetched from your origin.

You'll find it under **Cache → Prefetching cache**.

It's very useful when:

* You're about to launch something and expect a lot of traffic at once (a campaign, a release, a live event).
* You've just invalidated content and want the new version ready in every node before visitors request it.
* You have heavy content (large images, video segments, downloads) that you don't want your origin to serve on the first visit.

### Prefetching URLs

1. Click **New Prefetch**.
2. In the **Prefetch URLs** window, write the URLs you want to warm up in the **List of URLs** box, **one URL per line**:

```
   https://www.example.com/path/to/content
   https://www.example.com/path/to/another/content
   https://www.example.com/path/to/another/content/subcontent
```

3. Click **Prefetch**. **Discard** closes the window without doing anything.

Write each URL in full, starting with `https://` or `http://`. Don't use spaces or commas to separate them: only line breaks. If a line isn't a valid URL (for example, `www.example.com` without the protocol), the box turns red and shows *Invalid URL found*, and nothing is sent until you fix it.&#x20;

<figure><img src="https://782247050-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdLlfX5hLpgfTCKcNCR8i%2Fuploads%2FuAvw1Np1yK0LYUBDGuLZ%2FCaptura%20de%20pantalla%202026-10-29%20a%20las%2013.28.36.png?alt=media&amp;token=858da2ba-8dee-4cc5-9d9c-a9b044c50732" alt=""><figcaption></figcaption></figure>

### The Prefetching page

The page lists the prefetch requests you've made. For each one it shows:

| Column      | What it shows                                                                                                               |
| ----------- | --------------------------------------------------------------------------------------------------------------------------- |
| **ID**      | The identifier of the prefetch.                                                                                             |
| **Date**    | When it was requested, with day and time.                                                                                   |
| **User**    | The email of the user who requested it.                                                                                     |
| **URL**     | The URL that was prefetched, with a button to copy it. Long URLs are shortened; the copy button gives you the full address. |
| **Actions** | **Refetch** runs the prefetch again for that URL.                                                                           |

Each row corresponds to one URL, and the most recent ones appear first.

#### Repeating a prefetch

If you need to warm up the same URL again (for example, after invalidating it), you don't have to type it again: click **Refetch** in its row.

At the bottom of the list you can choose how many **rows per page** to show, see the total number of records and the time of the last update, turn on **Auto-refresh** to keep the list up to date, and move between pages.

The list keeps the history of your previous prefetches. If you haven't requested anything yet, the page says *No cache warm-ups yet* and offers **Warm up your first URLs**, which opens the same window as **New Prefetch**.

### Prefetching through the API

You can also request a prefetch from your own scripts or deployment pipelines, with a `POST` request that carries the list of URLs:

```
POST /v1/companies/<company_id>/prefetch/
```

json

```json
{
  "urls": [
    "https://www.example.com/path/to/content",
    "https://www.example.com/path/to/another/content"
  ]
}
```

Replace `<company_id>` with your company ID (for example, `c123`).

In case of doubts, please reference our [API documentation](https://api.transparentcdn.com/docs).


---

# 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.transparentedge.eu/getting-started/dashboard/prefetch.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.
