Upload API

An Upload is a temporary resource you create by uploading a file. It is the first step before creating a Media: when you upload a file, the response returns a single Upload, and you use this Upload's information to create a Media. Creating a Media happens on CMA (Weegloo User) or ACMA (Service User) and is outside the scope of this page.

An Upload is a temporary resource. It expires 24 hours after creation (expiresAt), and if you do not turn it into a Media within that window, it disappears. An Upload has no concept of publishing or versioning (no version, status, or publish properties). It also has no body fields, and carries only the system property sys. The base URL is https://upload.weegloo.com/v1, and every request requires a Bearer token that authenticates against Upload.

Resource structure

The following is the response for an Upload created by uploading a clothing-store product photo (a tumbler image) to a Space. It has only sys, which contains keys such as owner, expiresAt, and size.

{
  "sys": {
    "id": "4bgMfu7cFGYDRQn4jdqFICdQiCZ15W",
    "type": "Upload",
    "owner": { "sys": { "id": "tcq4V2Xb", "type": "Refer", "targetType": "Space" } },
    "createdBy": { "sys": { "id": "3p4tcFbQRwz503VXdtHXNI5dZH5TVB", "type": "Refer", "targetType": "User" } },
    "createdAt": "2026-06-18T04:51:53.903Z",
    "updatedBy": { "sys": { "id": "3p4tcFbQRwz503VXdtHXNI5dZH5TVB", "type": "Refer", "targetType": "User" } },
    "updatedAt": "2026-06-18T04:51:53.903Z",
    "expiresAt": "2026-06-19T04:51:53.903Z",
    "size": 50847
  }
}

Key properties:

• sys.id: The unique identifier of the Upload. You pass this value when creating a Media. It also goes into {uploadId} in the single-read and delete paths.
• sys.owner: A reference pointing to where this Upload belongs. Its targetType is Space or Organization (see Space and Organization contexts below).
• sys.expiresAt: The expiration time. It is 24 hours after createdAt, and once this time passes the Upload disappears.
• sys.size: The size of the uploaded file (in bytes). The example above is 50847 bytes.

System properties (sys)

Every Upload carries its system properties in the sys object. owner, createdBy, and updatedBy are in the Refer shape ({ "sys": { "id", "type": "Refer", "targetType" } }).

All 9 properties above are always included in the response. The version, status, and publish found in the sys of a Content or Content Type are not present in an Upload. That is because an Upload is not a resource that is published or versioned, but a one-time ingredient for creating a Media. Unlike the space of other resources, which points to a single kind, owner points to a Space or an Organization depending on targetType.

Space and Organization contexts

An Upload can be created in two contexts, and the path and sys.owner differ by context.

An Upload in the Space context is the ingredient for creating a Media in that Space. An Upload in the Organization context is used when you upload a file that is used directly by the organization, such as an organization icon. In both cases the resource structure returned in the response is the same; only the targetType value of sys.owner differs.

Upload methods: multipart and binary

There are two methods for the POST request that uploads a file. Either way, what comes back in the response is the same Upload resource.

The multipart method sends the request body as multipart/form-data. The file goes into a form field named file. It suits situations where you send form data, such as uploading directly from a browser's file-picker input.

The binary method puts the raw bytes of the file directly into the request body. There is no restriction on the body's media type (Content-Type) (usually application/octet-stream is used), and in the Space context you must also send the byte length of the body in the Content-Length header. It suits server-side code that transmits only the file bytes without a form structure.

API

The base URL for all endpoints below is https://upload.weegloo.com/v1, and a Bearer token that authenticates against Upload is required in the Authorization header. The 4 endpoints for the Space context come first, followed by the 4 for the Organization context.

Related documents

• Media: The request format for creating a Media from an uploaded Upload.
• Media (concept): How to work with file assets in the content studio.