The service information can be fetched via the following endpoint. This endpoint doesn’t provide filter parameters.
You can can fetch information about raw data objects by using the following endpoints.
Returns a list of raw data file information entries for all entities with type :entity. You further have to and restrict the request to the entities’ uuids by adding the following uri parameter:
Parameter name | Description Example |
---|---|
uuids |
Restricts the query to the entities identified by the given uuids. Entites of type ‘Value’ are identified by a compound key, which consists of the uuid of the measurement, ‘|’ and the characteristics uuid uuids={652ae7a0-d1e1-4ee2-b3a5-d4526f6ba822|78bd15c6-dc70-4ab4-bd3c-8ab2b5780b52} |
The returned objects contains the following properties:
Property | Description |
---|---|
TargetEntity target |
Specifies a concrete entity for a raw data object and consits of the entity’s type (Part, Characteristic, Measurement, Value) and guid. If raw data is attached to an entity of type Value , the uuid contains a compound key in the following format: {MeasurementUuid}|{CharacteristicUuid} |
int key |
This is a unique key that identifies this specific raw data object for a corresponding entity. An entity can have multiple raw data object that are distinct by this key. |
string fileName |
The filename of the raw data object. Please note that this filename is not unique (unlike filenames in traditional file systems). |
string mimeType |
The file’s mime type. |
DateTime lastModified |
The timestamp of the last modification of the corresponding raw data object |
DateTime created |
The timestamp of the creation of the corresponding raw data object |
int size |
The size of the raw data object in bytes |
string md5 |
The MD5-Hash of the raw data object |
You can can fetch, create, update and delete raw data objects by using the following endpoints.
The server caches raw data fetch requests. When you request a raw data file for the first time the response will contain the file itself and several HTTP headers. One of these headers is the ETag header. An ETag is a unique hash value to identify the file. It is a combination of the file’s MD5 checksum and the last modification date. If you send the ETag value in the If-None-Match header, the server can respond two different ways, depending in whether the file has been modified since the last request:
The requested raw data file
The requested thumbnail
You can attach files to all entity types: parts, characteristics, measurements and measured values.
An add request consists of 3 mandatory parts:
HTTP header variable | Description | Example Value |
---|---|---|
Content-Disposition | Includes the file name | “MetalPart.meshModel” |
Content-Length | Includes the length in bytes | 2090682 |
Content-MD5 | Includes file’s MD5 hash sum | “bdf6b06ab301a |
Content-Type | Includes file’s MIME type | “application/x-zeiss-piweb-meshmodel” |
When adding a file, you can pass the desired file key as part of the uri. If you pass -1 or no key, the next available key will automatically assigned by the server. (recommended)
If you pass a key which is already assigned to another file, this file will be replaced.
An update request consists of 3 mandatory parts:
HTTP header variable | Description | Example Value |
---|---|---|
Content-Disposition | Includes the file name | “MetalPart.meshModel” |
Content-Length | Includes the length in bytes | 2090682 |
Content-MD5 | Includes file’s MD5 hash sum | “bdf6b06ab301a |
Content-Type | Includes file’s MIME type | “application/x-zeiss-piweb-meshmodel” |