Skip to main content
PATCH
Continue Scan Upload

Authorizations

CORGEA-TOKEN
string
header
required

API key for authentication

Headers

Upload-Offset
integer
required

Current byte offset of the upload

Upload-Length
integer
required

Total size of the file in bytes

Upload-Name
string
required

Name of the file being uploaded

Path Parameters

transfer_id
string<uuid>
required

The transfer ID from the initial scan request

Body

multipart/form-data
chunk_data
file
required

The next chunk of data for the scan

project_name
string
branch
string
repo_url
string
sha
string
partial_scan
boolean
files_to_scan
string

Comma-separated list of files to scan

metadata
string

User-supplied scan metadata as a JSON object string, e.g. {"pipeline_url":"https://ci.example/run/123"}. Validated on every chunk request and attached to the scan once the upload completes. Must be a JSON object of at most 16,384 bytes; otherwise the request fails with 400.

Response

Chunk uploaded successfully

transfer_id
string<uuid>
status
string
Example:

"success"

message
string
Example:

"Chunk uploaded successfully."