# Upscrape Linktree Scraper LLM Integration Prompt

Give this to an LLM or coding agent. It must fetch the OpenAPI spec first and use this brief only for orientation.

## First Step

Fetch and read this OpenAPI spec before writing code:

https://data.upscrape.com/catalog/platforms/linktree/openapi.json?token=SFMyNTY.g2gDdAAAAAFtAAAAC3BsYXRmb3JtX2lkbQAAAAhsaW5rdHJlZW4GAEZ2C0qfAWIAAVGA.YXXF48aSXnTZlgcvLlKW8-ZD5IIlV25kqB-6ncvoS_w
This signed OpenAPI URL is valid for approximately 7 days.

## Hard Rules

- Use the OpenAPI spec as the source of truth for endpoints, request bodies, response bodies, errors, and JSON schemas.
- Do not infer fields from capability descriptions; fetch the spec and use its component schemas.
- Authenticate every request with `Authorization: Bearer YOUR_API_KEY`.
- Start runs with `POST /execute`; do not invent platform-specific execute endpoints.
- Poll `GET /jobs/{id}` or `GET /jobs/{id}/result` until `state` is `completed` or `failed`.
- Optionally send `Prefer: wait=N` on `POST /execute` to wait up to N seconds for inline results.
- If the response is `200`, the job completed — read `results[0].data`. If `202`, poll `GET /jobs/{id}`.
- `stream` is public-facing but must remain `false` today.

## API Base

- Base URL: `https://data.upscrape.com`
- OpenAPI spec: `https://data.upscrape.com/catalog/platforms/linktree/openapi.json?token=SFMyNTY.g2gDdAAAAAFtAAAAC3BsYXRmb3JtX2lkbQAAAAhsaW5rdHJlZW4GAEZ2C0qfAWIAAVGA.YXXF48aSXnTZlgcvLlKW8-ZD5IIlV25kqB-6ncvoS_w`
- Execute endpoint: `POST /execute`
- Job poll endpoint: `GET /jobs/{id}`
- Result alias: `GET /jobs/{id}/result`
- Content-Type: `application/json`
- Optional header: `Idempotency-Key`
- Optional header: `Prefer: wait=N` (hold connection up to N seconds for synchronous result)

## Execution Flow

1. Send `POST /execute` with a platform capability ID and its `input` object.
2. The API responds with a queued `job_id`.
3. Poll the job endpoint until `state` becomes `completed` or `failed`.
4. If completed, read `results[0].data`; its exact shape is defined by the OpenAPI component schema for the selected capability.

## Example Execute Request

```json
{
  "capability": "linktree.directory.get",
  "input": {
    "category": "all",
    "page": 1
  }
}
```

## Optional Request Fields

- `network.session_id`: explicit reusable session identifier
- `network.session_key`: stable key used to derive a reusable session
- `network.sticky`: reuse the resolved session when `true`
- `timeout_ms`: per-capability timeout override up to the capability maximum listed below
- `stream`: must be `false`

## Supported Capabilities

- `linktree.directory.get` - Get Directory Page. Fetch one page (up to 18 profiles) of the Linktree public profile directory, filtered by category Max `timeout_ms`: 30000. Streaming: disabled.
- `linktree.directory.profiles` - Harvest Directory Profiles. Harvest profiles across many directory pages in a single call. Sync mode collects all profiles; stream mode emits one profile per event Max `timeout_ms`: 120000. Streaming: supported.
- `linktree.profile.get` - Get Profile. Fetch a Linktree profile: display name, bio, email, country, tier, verification, social handles, and all content links Max `timeout_ms`: 30000. Streaming: disabled.