Name: FileShare
Author: FileShare

Introduction

The FileShare API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

Authentication

The FileShare API uses OAuth 2.0 bearer tokens for authentication. You can generate a bearer token by exchanging your Client ID and Client Secret via the `/auth` endpoint.

curl -X POST https://api.filesharefast.com/v1/auth \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_CLIENT_SECRET" \
  -d "grant_type=client_credentials"

Keep your tokens secure

Your API tokens carry many privileges. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so forth.

POSTCreate Upload URL

To upload a file, you must first request a pre-signed S3 URL. This ensures secure, direct-to-cloud transfers without bottlenecking your servers.

Endpoint

https://api.filesharefast.com/v1/files/presign

Example Request

cURLJavaScript

curl -X POST https://api.filesharefast.com/v1/files/presign \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "filename": "report_2026.pdf",
    "filesize": 1048576,
    "contentType": "application/pdf"
  }'

Request Parameters

Name	Type	Description
filename	string	Required. The original name of the file.
filesize	integer	Required. The size of the file in bytes.
contentType	string	Optional. The MIME type of the file (e.g., application/pdf).

Rate Limits

To ensure platform stability, the API is subject to rate limiting.

Free Tier: 100 requests per minute
Pro Tier: 1,000 requests per minute
Business Tier: Custom rate limits available

API Documentation