...
You can also use x-eagle-correlation-id HTTP header to specify your correlation id.
AdhocReport GET
...
Endpoint in MC2
...
This endpoint redirects requests to the existing AdhocReport POST endpoint transforming the GET parameters into the JSON HTTP body and allows using the use of HTTP GET parameters like as shown in the examples below.
Let's take the next uri as an exampleExample:
https://host:port/eagle/report/v1/adhocReport?reportName=RM_PerfTotalExtended&entityId=41038M&beginDate=20150101&endDate=20151231&fields=1 Yr Net Return vs BM,10 Yr Annual Net Return vs BM&outputFormat=JSON
The HTTP parameters will be are taken as is and transformed into the JSON HTTP body:
...
body and redirected to the AdhocReport POST endpoint: http://host:port/eagle/report/v1/adhocReport.
| Code Block | ||
|---|---|---|
| ||
{ "reportName": "RM_PerfTotalExtended", |
...
"entityId": "41038M", |
...
"beginDate": "20150101", |
...
"endDate": "20151231", |
...
"fields": "1 Yr Net Return vs BM,10 Yr Annual Net Return vs BM", |
...
"outputFormat":"JSON" |
...
} |
and redirected to the AdhocReport POST endpoint:
http://host:port/eagle/report/v1/adhocReport
If "fields" If the fields parameter is empty/not present in uri: httpthe url then it is empty in the JSON body., For example: http://host:port/eagle/report/v1/adhocReport?reportName=RM_PerfTotalExtended&entityId=41038M&beginDate=20150101&endDate=20151231&outputFormat=JSON
then it will be empty in JSON body:
...
.
| Code Block | ||||
|---|---|---|---|---|
| ||||
{ "reportName": "RM_PerfTotalExtended", |
...
"entityId": "41038M", |
...
"beginDate": "20150101", |
...
"endDate": "20151231", |
...
"fields": "", |
...
"outputFormat":"JSON" |
...
} |
As in the case with AdhocReport POST endpoint above there is possibility to , you can use x-eagle-return-ticket, x-eagle-rest-callback and x-eagle-correlation-id HTTP headers.