file.kiwi valid

api.file.kiwi v2

Use this API when a user needs a file.kiwi link for browser-based file transfer.

For agents: api.file.kiwi v2: API for creating file.kiwi links for browser-based file transfer.

file transferfile.kiwi linksbrowser file sharingfile transfer api

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T10:10:37.939Z. Cached copy · Source on file.kiwi

# api.file.kiwi v2

Use this API when a user needs a file.kiwi link for browser-based file transfer.

Base URL: https://api.file.kiwi
Documentation: https://file.kiwi/api
OpenAPI: https://api.file.kiwi/openapi.json
Pricing: https://file.kiwi/price
Machine-readable pricing: https://file.kiwi/pricing.json

No authentication is required.

The machine-readable pricing catalog uses stable USD reference prices and includes exact file-size boundaries, add-on formulas, and bulk-discount thresholds. The human pricing page may display localized prices and purchasing-power adjustments.

## Create an empty WebFolder link

Call `POST /v2/folders` without `files[]`. This creates an empty WebFolder and returns a share URL. The user uploads files later in the browser through `file.kiwi`.

Do not register files through the API for this flow. Do not call upload-status endpoints for this flow.
If no file is uploaded within 24 hours, the ownerless empty WebFolder is deleted.

### Endpoint

```http
POST https://api.file.kiwi/v2/folders
Content-Type: application/json
```

### Request

```json
{
  "title": "Large file transfer",
  "mode": "send"
}
```

`title` is optional. `mode` is optional and defaults to `send`.

### Choose the mode

- Use `send` when the user wants to send large files to another person. The first browser uploader becomes the folder owner, and recipients download the uploaded files.
- Use `share` when collaborators need to exchange files with each other. Browser users can upload and download through the same folder.

Do not choose `request` for this empty-folder assistant flow. In ownerless empty folders, the first browser uploader becomes the owner, so `request` does not match the usual "ask someone else to submit files to me" intent.

### Response

```json
{
  "folderId": "9268b452",
  "folderUrl": "https://file.kiwi/9268b452#KkV0sRAexWGN4ksu2p98oQ",
  "folderUrlBase": "https://file.kiwi/9268b452",
  "mode": "send",
  "uploadRequiredWithinHours": 24,
  "files": []
}
```

Return `folderUrl` to the user.
…

Related sites

Other listed sites in APIs and SDKs. See the whole category →

Machine-readable: GET /v1/resolve?q=file.kiwi · GET /v1/domain/file.kiwi · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for file.kiwi:
1. POST https://agentwebmap.com/v1/sites/file.kiwi/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://file.kiwi/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/file.kiwi/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/file.kiwi).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.