Upload a file
POST/v1/projects/:project_id/files/upload
Uploads a file to the server and stores it in the configured storage directory
Request
Responses
- 201
- 400
- 401
- 403
- 404
- 409
- 413
- 429
- 500
- 502
- 4XX
File uploaded successfully
Missing file or invalid project
Missing or invalid credentials.
The credential is scoped to a different project, or the caller's role in the project does not carry this action.
The project does not exist or the caller is not a member of it (RESOURCE_NOT_FOUND).
The project's storage_bytes quota is exceeded (QUOTA_STORAGE_EXCEEDED). Delete stored content, or raise the quota — no window reset clears a stored total, so no Retry-After is sent.
The upload is over this deployment's byte ceiling (UPLOAD_TOO_LARGE; FILE_UPLOAD_MAX_BYTES, 25 MB by default). The request is refused while the body is still streaming, so nothing was stored.
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there