Uploads

Upload files to netiks cloud, get the files from your account or using APIs in Assets

Upload Single file

To upload Single file, use Mode 1: Single File Upload

Upload File (Single File Upload or Confirm Upload)

post

https://prod.backend.netikscloud.comhttps://netiks.s3.amazonaws.com

/api/v1/assets/developer-upload-file/

This endpoint supports two upload modes:

Mode 1: Single File Upload

• Use Content-Type: multipart/form-data

• Upload file directly in the request body as form data

• The file will be processed and stored immediately

Mode 2: Confirm Upload

• Use Content-Type: application/json

• Confirm a file that was previously uploaded via presigned URL

• Include is_presigned: true along with storage details in the JSON body

Both modes return the same response format with asset details upon successful upload.

Header parameters

Content-Typestring · enumRequired

Use 'multipart/form-data' for direct upload or 'application/json' for presigned confirmation

Possible values:

x-api-keystringRequiredExample: ne-zwpVh1idj6InYwTWk866n1qrf

Body

multipart/form-dataapplication/json

filestring · binaryRequired

The file to upload directly

Responses

201

File uploaded successfully (either directly or via presigned confirmation)

application/json

403

API Key Missing

application/json

post

/api/v1/assets/developer-upload-file/

HTTPcURLJavaScriptPython

POST /api/v1/assets/developer-upload-file/ HTTP/1.1
Host: prod.backend.netikscloud.com
x-api-key: text
Content-Type: multipart/form-data
Accept: */*

multipart/form-dataapplication/json

{
  "message": "text",
  "asset": {
    "id": "text",
    "asset_name": "text",
    "storage_url": "text",
    "location": null,
    "location_name": null,
    "format": "text",
    "file_size": 1,
    "dimensions": null,
    "access": "text",
    "created_by": "text",
    "last_updated_by": "text",
    "created_at": "2026-03-19T12:20:01.485Z",
    "last_updated": "2026-03-19T12:20:01.485Z"
  }
}

Bulk Upload

This is a three step process

Generate Presigned URL

For bulk uploads, it's best to do so by client—start by generating a presigned URL.

Generate Presigned URLs

post

https://prod.backend.netikscloud.comhttps://netiks.s3.amazonaws.com

/api/v1/assets/developer-generate-presigned-url/

Header parameters

Content-TypestringOptionalExample: application/json

x-api-keystringRequiredExample: ne-zwpVh1idj6InYwTWk866n1qrf

Body

application/json

Responses

200

Generate Presigned URLs

application/json

403

Storage Space Limit Error

application/json

post

/api/v1/assets/developer-generate-presigned-url/

HTTPcURLJavaScriptPython

POST /api/v1/assets/developer-generate-presigned-url/ HTTP/1.1
Host: prod.backend.netikscloud.com
x-api-key: text
Content-Type: application/json
Accept: */*
Content-Length: 67

{
  "files": [
    {
      "name": "test-image.jpg",
      "type": "image/jpeg",
      "size": 32
    }
  ]
}

{
  "presigned_urls": [
    {
      "file_name": "text",
      "presigned_url": "https://example.com",
      "storage_url": "text",
      "s3_path": "text",
      "content_type": "text"
    }
  ]
}

Upload File using Presigned URL

Next, you will upload the actual files by making a PUT request to the generated presigned URL you got in the previous API - POST /api/v1/assets/developer-generate-presigned-url/. This URL is a secure, 15 minutes limited link that allows you to send the file directly to the storage server.

Upload File using Presigned URL

put

Query parameters

X-Amz-AlgorithmstringRequired

X-Amz-CredentialstringRequired

X-Amz-DatestringRequired

X-Amz-ExpiresintegerRequired

X-Amz-SignedHeadersstringRequired

X-Amz-SignaturestringRequired

Header parameters

Content-TypestringOptionalExample: image/jpeg

Body

image/jpegapplication/octet-stream

string · binaryOptional

Responses

200

Upload File using Presigned URL

put

/generated_presigned_url

HTTPcURLJavaScriptPython

PUT /generated_presigned_url?X-Amz-Algorithm=text&X-Amz-Credential=text&X-Amz-Date=text&X-Amz-Expires=1&X-Amz-SignedHeaders=text&X-Amz-Signature=text HTTP/1.1
Host: netiks-cloud-asset-prod.s3.amazonaws.com/
Content-Type: image/jpeg
Accept: */*
Content-Length: 28

"(binary JPEG file content)"

image/jpegapplication/octet-stream

200

Upload File using Presigned URL

No content

Confirm Upload

Lastly, confirm the upload by sending the details obtained from the Generate Presigned URL API. This step ensures that the system registers the uploaded file. Use Mode 2: Confirm Upload

Upload File (Single File Upload or Confirm Upload)

post

https://prod.backend.netikscloud.comhttps://netiks.s3.amazonaws.com

/api/v1/assets/developer-upload-file/

This endpoint supports two upload modes:

Mode 1: Single File Upload

• Use Content-Type: multipart/form-data

• Upload file directly in the request body as form data

• The file will be processed and stored immediately

Mode 2: Confirm Upload

• Use Content-Type: application/json

• Confirm a file that was previously uploaded via presigned URL

• Include is_presigned: true along with storage details in the JSON body

Both modes return the same response format with asset details upon successful upload.

Header parameters

Content-Typestring · enumRequired

Use 'multipart/form-data' for direct upload or 'application/json' for presigned confirmation

Possible values:

x-api-keystringRequiredExample: ne-zwpVh1idj6InYwTWk866n1qrf

Body

multipart/form-dataapplication/json

filestring · binaryRequired

The file to upload directly

Responses

201

File uploaded successfully (either directly or via presigned confirmation)

application/json

403

API Key Missing

application/json

post

/api/v1/assets/developer-upload-file/

HTTPcURLJavaScriptPython

POST /api/v1/assets/developer-upload-file/ HTTP/1.1
Host: prod.backend.netikscloud.com
x-api-key: text
Content-Type: multipart/form-data
Accept: */*

multipart/form-dataapplication/json

{
  "message": "text",
  "asset": {
    "id": "text",
    "asset_name": "text",
    "storage_url": "text",
    "location": null,
    "location_name": null,
    "format": "text",
    "file_size": 1,
    "dimensions": null,
    "access": "text",
    "created_by": "text",
    "last_updated_by": "text",
    "created_at": "2026-03-19T12:20:01.485Z",
    "last_updated": "2026-03-19T12:20:01.485Z"
  }
}