Skip to main content
Manage project files when work needs source, assets, uploads, or search.

​
Steps

  1. Read or write project files.
  2. Use branches when file changes need review or release flow.
  3. Upload assets that the project needs.
  4. Search project content before changing or generating files.

​
Try it with REST

List project files: GET /projects/{project_reference}/files
Terminal
curl https://api.veryfront.com/projects/support-assistant/files \
  -H "Authorization: Bearer $VERYFRONT_API_KEY"
Create an upload URL: POST /projects/{project_reference}/uploads
Terminal
curl -X POST https://api.veryfront.com/projects/support-assistant/uploads \
  -H "Authorization: Bearer $VERYFRONT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "file_path": "assets/example.txt",
    "content_type": "text/plain",
    "size": 128
  }'

​
API surfaces

SurfaceStart here
RESTFiles, Uploads, Search
GraphQLFiles, Create File Upload URL
MCPList Files, Create Upload URL

​
Verify

Confirm the file appears in project file search. Use the returned upload URL with the required headers before referencing the asset.

​
File surfaces

SurfaceUse it for
FilesProject source and assets.
Branch filesReviewable file changes.
Release filesFiles attached to a release.
UploadsUploaded assets and generated artifacts.
SearchProject content lookup.

​
API reference

APIUse
RESTFiles, branches, release files, uploads, and search.
GraphQLFile, branch, upload, and search views.
MCPFile, upload, branch, and search tools.