| GET | /files/{UserId} |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserId | path | Guid | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Eras2FileInfos | form | List<Eras2FileInfo> | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Guid | form | Guid | No | |
| Name | form | string | No | |
| FileType | form | string | No | |
| ObjektGuid | form | Guid? | No | |
| NutzerGuid | form | Guid? | No | |
| ChecksumMD5 | form | byte[] | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /files/{UserId} HTTP/1.1
Host: g-lange-servdesk.eras-online.de
Accept: text/jsv
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
eras2FileInfos:
[
{
Guid: 00000000000000000000000000000000,
Name: String,
FileType: String,
ObjektGuid: 00000000000000000000000000000000,
NutzerGuid: 00000000000000000000000000000000,
Checksum: AA==
}
],
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
}
}