# Curl for object upload Upload is a multipart request towards Open Content **/opencontent/objectupload** endpoint. ## Curl Below is how a curl request for upload can look like: ``` /usr/bin/curl \ http://:8080/opencontent/objectupload \ -u admin:admin \ -F id= \ -F batch= \ -F file= \ -F file-mimetype= \ -F =@ \ -F metadata= \ -F metadata-mimetype=npexchange/article \ -F =@ \ -F metadata2= \ -F metadata2-mimetype=npexchange/article \ -F =@ \ -F preview=.jpg \ -F preview-mimetype=image/jpg \ -F .jpg=@.jpg \ -F thumb=.jpg \ -F thumb-mimetype=image/jpg \ -F .jpg=@.jpg \ -F source= ``` | Field | M/O | Description | | ----------------------------------------- | :----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | -F id=\ | O | The desired Uiid for the uploaded content object. Open Content will return the given id for the uploaded content. | | -F batch=\ | O | Default = false, used to upload content that should be indexed later using the batch indexing mechanism. | | -F file=\ | M | The File Name of the uploaded content. | | -F file-mimetype=\ | M | Mime type for the uploaded content. | | -F \=@\ | M | \ is the same as the given file=\, the file itself | | -F metadata=\ | M | Meta Data file | | -F metadata-mimetype=\ | M | Meta Data Mime type | | -F \=@\ | M | The Meta Data file | | -F metadata2=\ | O | If multiple meta data files should be uploaded, use this syntax with index starting at 2. | | -F metadata2-mimetype2=npexchange/article | O | | | -F \=@\ | O | | | -F preview=\.jpg | | File name for preview image | | -F preview-mimetype=\ | | Mime type for the preview image | | -F \.jpg=@\.jpg | | The Preview image | | -F thumb=.jpg | | File Name for the image thumbnail | | -F thumb-mimetype=\ | | Mime type for the image thumbnail | | -F \.jpg=@\.jpg | | The image thumbnail | | -F source=\ | | Set the property source to the given value. Please note that the value of this property not can be re-created during a re-index process. | | *-F reuseFiles=\* | *(\*)* | *If true, the object will get its files from one of the registered storages. Any files in the HTTP request will be ignored. This is used in eventlog replication for example.* | | *-F version=\* | *(\*)* | *The version of the of the object where files should be reused* | | *-F created=\* | *(\*)* | *The created date of the of the object where files should be reused, format: YYYY-MM-ddTHH:mm:ssZ, example: 2017-05-15T04:41:45Z* | | *-F updated=\* | *(\*)* | *The updated date of the of the object where files should be reused, format: YYYY-MM-ddTHH:mm:ssZ, example: 2017-05-15T04:41:45Z* | | *-F eventtype=\* | *(\*)* | *Possible values: ADD UPDATE DELETE* | | -H "If-Match:\" | | Enables optimistic locking. This upload will fail if the current object checksum does not match this e-tag. After upload the new e-tag will be returned in response header "ETag" | {% hint style="info" %} (\*) Is used by the Open Content Replicator when performing replications towards a read only Open Content server {% endhint %} | Http statuscode | Description | | --------------- | ------------------------------------------------------------------------------------------------ | | 200 | Upload was successful and the object has been updated. The HTTP response body contains the uuid. | | 201 | Upload was successful and an object has been created. The HTTP response body contains the uuid. | | 400 | Upload failed because of an invalid request. The HTTP response body contains the error message. | | 401 | Authentication is missing or is incorrect | | 409 | Upload failed because it is part of batch indexing. | | 412 | Upload failed because the E-Tag doesn't match the checksum of the object. | | 500 | Internal server error, unexpected error. The HTTP response body contains the error message. |