> For the complete documentation index, see [llms.txt](https://docs.console.zenlayer.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.console.zenlayer.com/welcome/cn/content-delivery-network/purge-and-prefetch/purge-api.md).

# 刷新 API

将刷新功能集成到自定义工具中。

1. 点击 **Add Token**。

   <div align="left"><figure><img src="/files/xOvJ98OVUekZiZt5y0yw" alt=""><figcaption></figcaption></figure></div>
2. 选择域名。
3. 点击 **Apply**。\
   API 用户名和密码将自动生成在下方。
4. 点击 **Add**。

   <div align="left"><figure><img src="/files/qOl0ySGTF8I8kPxWtMvk" alt="" width="375"><figcaption></figcaption></figure></div>
5. 点击 刷新 查看详细信息。

   <div align="left"><figure><img src="/files/r1m6zwA055sE1FarOu1F" alt="" width="375"><figcaption></figcaption></figure></div>

   <div align="left"><figure><img src="/files/lLWFG345UylppsbiurLy" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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.console.zenlayer.com/welcome/cn/content-delivery-network/purge-and-prefetch/purge-api.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.
