| GET | /api/v1/eras2files/{Guid} |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| BearerToken | query | string | Yes | |
| Guid | path | Guid | Yes |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Eras2File | form | Eras2File | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Guid | form | Guid | No | |
| Name | form | string | No | |
| FileType | form | Eras2FileType | No | Allowable Values
|
| ObjektGuid | form | Guid? | No | |
| NutzerGuid | form | Guid? | No |
| DSatz | |
| Hka | |
| E835Satz | |
| E898Satz | |
| Abrechnung | |
| ArgeSatz | |
| NutzerFile | |
| DevicePdf |
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 /api/v1/eras2files/{Guid} HTTP/1.1
Host: immo-account-servdesk.eras-online.de
Accept: text/jsv
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
eras2File:
{
Guid: 00000000000000000000000000000000,
Name: String,
FileType: DSatz,
ObjektGuid: 00000000000000000000000000000000,
NutzerGuid: 00000000000000000000000000000000
},
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
}
}