Read one file's content

GET

/sites/{pageId}/files/{path}

Returns one file's raw bytes, base64-encoded — READ-ONLY content inspection for abuse investigation. Readable for kind site and kind html alike — for a one-file HTML page that is its single index.html entry. path is checked against the site's own file listing first, never read from storage on an arbitrary caller-supplied key: a path absent from the listing 404s with FileNotFound, distinct from PageNotFound (the site itself wasn't found). Refused with 413 for a file larger than the inspection ceiling (the same size a single file edit is already allowed to be) — list the file's sizeBytes first via GET /sites/{pageId}/files if you need to check before requesting. Refused with 403 if the subject is not in good standing (see Forbidden) — this applies to reads as well as writes.

Request

Authorization

API Key

Add parameter in header

x-api-key

Example:

x-api-key: ********************

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Responses

🟢200OK

application/json

The file's content.

Bodyapplication/json

🟠401Unauthorized

🟠403Forbidden

🟠404Record Not Found

🟠413

🟠429

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://upload.tf/api/v1/sites/a1b2c3d4e5/files/assets/app.js' \
--header 'x-api-key: <api-key>'

Response Example

200 - Example 1

{
    "success": true,
    "data": {
        "path": "string",
        "sizeBytes": 0,
        "contentType": "string",
        "isEntry": true,
        "contentBase64": "string"
    }
}

Modified at 2026-08-25 00:05:47

List a site's files

Per-subject usage for a period