...
Version Note: Since version 8.3 it is also possible to have e unique photoID field in the metadata-JSON of the request.
Version Note: Since version 9.1.04 it is also possible to have e unique doSyncCheck field in the metadata-JSON of the request.
- doSyncCheck optional Parameter. (default = true)
If set to false, the check if the photo has already been transferred is omitted.
Important: Regardless of the setting of this parameter the photo will still not be accepted if a photo with this ID exists in the database.
Parameter
Name | Type | Since version | Required | Value(s) |
---|
apisid | string | 7.4 | yes | Excerpt Include |
---|
| URL Parameter to identify a photo |
---|
| URL Parameter to identify a photo |
---|
nopanel | true |
---|
|
|
...
Result:JSON
Name | Type | Since version | Example value |
---|
apisid | string | 7.4 | Session-ID returned from createWebApiSession |
processedFiles | array | 7.4 | Each array element has the following members
Name | Type | Since version | Value |
---|
fileName | string | 7.4 | The filename used on the PicApport Server | contentType | string | 7.4 | image/jpeg for .jpg Files | sizeInBytes | int | 7.4 | The size of the file in bytes | photoID | string | 7.4 | The unique PicApport photoID created after the upload. This ID may be used to access the photo. | doSyncCheck | boolean | 9.1.04 | optional Parameter. (default = true) If set to false, the check if the photo has already been transferred is omitted. Important: Regardless of the setting of this parameter the photo will still not be accepted if a photo with this ID exists in the database. | result | string | 7.4 | - OK
Photo was uploaded successfully - Server Error: File too big.
File was too big (see configuration parameter upload.max.filesize.mb) - Server Error: Invalid content type
currently only image/jpeg is supported
|
|
...