Let ChatGPT or Claude publish pages for you

Connect once and your AI can publish an HTML file as a shareable page, update it later with the same link, add a poll or a form, and read the comments that come back. No keys to copy. It signs in with your FileShare Pro account, and you can disconnect it any time.

Forms and polls with no code

Any page you publish can collect responses. Give a form one attribute and the page does the rest; add an element with data-fsp-results to show a poll's tally. Responses are visible only to you and the people on the file, in the document view and as CSV. The world can only submit, one bounded row at a time; a poll exposes counts for the one field you declared, never rows.

<form data-fsp-form="lunch" data-fsp-poll="choice" data-fsp-thanks="Thanks for voting!">
  <label><input type="radio" name="choice" value="Pizza"> Pizza</label>
  <label><input type="radio" name="choice" value="Tacos"> Tacos</label>
  <button>Vote</button>
</form>
<div data-fsp-results="choice" data-fsp-form="lunch"></div>

Authentication

Create a token in the app under Connect → Advanced and send it as a bearer credential. Tokens start with fsp_ and carry your full account access. The only thing a token cannot do is manage tokens. Connected apps get the same kind of token through OAuth 2.1 (discovery at /.well-known/oauth-authorization-server, dynamic registration, PKCE).

curl https://fileproapp.com/api/me \
  -H "Authorization: Bearer fsp_your_token_here"

Uploading a file

Three steps: declare the file, PUT the bytes to the presigned URL, confirm. A file that is never confirmed is never served. Optional workspace_id and folder_id put it somewhere on the way in.

# 1. Declare — returns file_id, slug and a presigned upload_url
curl -X POST https://fileproapp.com/api/files \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"file_name": "page.html", "size_bytes": 4096, "content_type": "text/html"}'

# 2. Upload the bytes (no auth header — the URL itself is the credential)
curl -X PUT "$UPLOAD_URL" -H "Content-Type: text/html" --data-binary @page.html

# 3. Confirm — the share link goes live
curl -X POST https://fileproapp.com/api/files/$FILE_ID/complete -H "Authorization: Bearer $TOKEN"

Files

PATCH accepts visibility (public · expiring · disabled), expires_at, password (empty string removes it), comments_enabled, comments_visibility (approval · open), suggestions_enabled, forms_enabled.

disabled turns the public link off and leaves the file open to the owner and to everyone added under /members. A password is a way in for people who were never added; those who were get in without it. For either, the file list returns a short-lived k — append it to the raw URL to load the page bytes.

The document

Comments

Forms

Media assets and mini-sites

MCP tools

The hosted server at https://fileproapp.com/mcp exposes: upload_file, list_files, get_file, replace_file, delete_file, set_link, move_file, list_workspaces, file_stats, list_comments, review_queue, approve_comment, list_submissions, poll_results, account_info. Content travels as text, up to 10 MB. The fsp CLI runs the same tools locally over stdio (fsp mcp).

Conventions

• Errors are JSON: {"error": "what went wrong"} with a meaningful status. A 403 with "upgrade": true means the plan, not the request.
• Writes are rate-limited per account. Back off on 429; the window is about a minute.
• IDs are UUIDs. Share links are fileproapp.com/v/<slug>; raw content is on r.fileproapp.com. The API answers on fileproapp.com and file-share-pro.com.
• The API and connected apps are open to every beta account; after beta they are Basic and up.