Extract Links from URL LLM Markdown

Back to Details
# Extract Links from URL

Extract links and destinations from a public webpage.

## API Overview

- **HTTP Protocol:** HTTPS
- **HTTP Method:** GET
- **HTTP Endpoint:** https://api.gugudata.io/v1/websitetools/url2links
- **Response Type:** application/json; charset=utf-8
- **DEMO Endpoint:** https://api.gugudata.io/v1/websitetools/url2links/demo
- **Live Demo:** https://gugudata.io/demo/url2links
- **Postman:** https://www.postman.com/gugudata/gugudata-io
- **LLM Page:** https://gugudata.io/details/url2links/llm
- **Raw Markdown:** https://gugudata.io/details/url2links/llm.md

## Remote MCP

- **MCP Endpoint:** https://mcp.gugudata.io/mcp
- **MCP Guide:** https://gugudata.io/mcp/
- **Authorization:** OAuth authorization opens in the browser; do not paste appkeys into MCP clients.
- **Tool Scope:** MCP clients receive GuGuData API tools available to the authorized account.

## Data & API Features

- Webpage link extraction: Collect link strings from a public webpage with one request.
- Ordered results: Receive links in returned order, without removing duplicates.
- Entry counts: Read the number of extracted entries alongside the list.
- Content inventories: Prepare references for documentation and content reviews.
- Navigation review: Inspect a page's links as input to your own review workflow.
- Simple integration: Submit a URL and receive a JSON result for further processing.

## API Request Parameters

| Name | Type | Is Required | Default Value | Remark |
| --- | --- | --- | --- | --- |
| appkey | string | true | YOUR_APPKEY | API key used to authenticate the request. |
| url | string | true |  | Target webpage URL. |

## API Response Parameters

| Name | Type | Remark |
| --- | --- | --- |
| result | array<string> | Links extracted from the webpage, in the order returned by the page. |
| count | integer | Number of links returned in result. |
| requestParameter | string | Privacy-safe summary of the requested webpage. |

## API Response Status Codes

| Status Code | Explanation of Status Code | Remarks |
| --- | --- | --- |
| 200 | Request processed successfully. | Some endpoints expose a separate application-level status field in the response body, such as `dataStatus.statusCode`. |
| 400 | Invalid request parameters or request format. | Check required fields, data types, and request body format. |
| 401 | Missing or unknown application key. | Provide a valid `appkey` with the request. |
| 403 | The application key is recognized but access is not allowed. | The key may be expired, inactive, or not permitted for the requested API. |
| 429 | Request rate or trial usage limit exceeded. | Reduce request frequency and retry with backoff. If a trial allowance is exhausted, check Trial Keys for remaining requests and subscribe to continue. |
| 500 | Internal service error. | Retry later or contact support if the error persists. |
| 503 | Upstream service unavailable. | Retry later; the requested upstream dependency is temporarily unavailable. |

## cURL Example

```bash
curl --location 'https://api.gugudata.io/v1/websitetools/url2links?appkey=YOUR_APPKEY&url=YOUR_VALUE'
```