Developer API

Authentication

Every request needs an Authorization header with a Bearer token. Generate a key from your account page.

Authorization: Bearer ftu_live_...

Upload a file

POST https://filetourl.org/api/public/v1/upload

Send a multipart/form-data body with a single field named file.

curl -X POST https://filetourl.org/api/public/v1/upload \
  -H "Authorization: Bearer ftu_live_YOUR_KEY_HERE" \
  -F "file=@/path/to/local/file.pdf"

Success (200):

{
  "url": "https://filetourl.org/f/abc12xyz",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "tier": "pro"
}

Errors:

• 401 — missing/invalid/revoked API key
• 403 — key's account is no longer on the Developer plan
• 400 — no file in the request body
• 413 — monthly data cap reached
• 429 — monthly call cap reached

MCP (for AI agents)

Prefer to use this from an AI agent like Claude Code or Cursor? Connect via MCP instead of raw HTTP calls. Same API key, same limits.

Add this to your MCP client config:

{
  "mcpServers": {
    "filetourl": {
      "url": "https://filetourl.org/api/mcp",
      "headers": { "Authorization": "Bearer ftu_live_YOUR_KEY_HERE" }
    }
  }
}

Tools:

• upload_file — upload a file (base64) and get back a permanent short URL. Counts against your monthly call and data caps.
• get_file_status — check whether a previously uploaded file's link is still live. Read-only, doesn't count against caps.

Rate limits

• 2,000 API calls per month, per key
• 25 GB of upload data per month, per key
• Rolling 30-day window (resets 30 days after your first call)
• Requires the Developer plan (£48/yr)