Upserting filesΒΆ

The unique file_id is used to update an uploaded file or create a file if file_id does not exist.

PUT /v1/file/(file_id)

Upsert a file with a given file_id.

Example request:

Content-Type: image/png
Authorization: Bearer <token>


Example response:

HTTP/1.1 200 OK
Content-Type: application/json

  "file_id": "05c40f1e-cdaf-4e29-8976-38c899",
  "content_type": "image/png",
  "file_status": "uploaded",
  "file_size": 351667,
  "user_id": 42,
  "user_role": "user",
  "created_at": "2017-04-25T08:26:22.834266+00:00"

Authorization header is not required if the request is being made from a browser, since Cookie will be set.


By default, File APIs are only accessible to those users with admin role. Goto Permissions tab under File Service in the console and enable Private webhook to enable user role also to upload and download files. This default permissions are based only on role and not on user ID. Hence, anybody with a user role can download a file another user has uploaded. For a more fine grained access control, refer to Authorization webhooks.

Uploaded files will be visible on the API console..

For more details, see API reference.