On This Page:
| Table of Contents |
|---|
Application Server REST Endpoints
...
The Swagger UI REST Endpoint is exposed on 2017R2 and later environments at https://webserver/mc2/swagger-ui.html
...
Execute Extract Service REST Requests
To execute an extract, you can use the SWAGGER definition to see all resource endpoints and parameters supported to build the URL. You can use either a Web Browser or a command line tool, such as curl, to execute REST requests.
...
In 2017R2, this is the format:
http://webserver/eagle/v2/entities?maxrows=1
To retrieve the result in EagleML, you can specify the output format as:
http://appserverhostname:20427/eagle/v2/entities?maxrows=1&outputformat=eagleml
To retrieve the extract compressed, you can specify the output format by appending +gzip:
http://appserverhostname:20427/eagle/v2/entities?maxrows=1&outputformat=eagleml+gzip
or
http://appserverhostname:20427/eagle/v2/entities?maxrows=1&outputformat=json+gzip
For a list of supported endpoints for EagleML extracts and their parameters/swagger files, see REST API Extracts.
...
Eagle Data Services REST Requests
The You can execute the Eagle Data Services extracts can be executed thru through the EQL endpoint (http://webserver/eagle/v2/eql/api-doc) or thru or through the Generic Extract REST API (http://webserver/eagle/v2/generic/extract/api-doc).
An example of execution is included at at Running Data Services Extracts Using REST Requests.