Send Requests
Use these guidelines when sending requests using the REST API for Embedded R Execution.
URL Structure
Here's the URL structure for requests:
https://<oml-cloud-service-location-url>.oraclecloudapps.com
In the URL, <oml-cloud-service-location-url>
contains the tenancy ID, region, and database name.
An example URL is the following:
https://qtraya2braestch-omldb.adb.us-sanjose-1.oraclecloudapps.com
qtraya2braestch
is the tenancy IDomldb
is the database nameus-sanjose-1
is the region
Supported Methods
You can perform operations on REST API for Embedded R Execution endpoints by using standard HTTP method requests, as summarized in the following table.
HTTP Method | Description |
GET |
Retrieve metadata about the versions of the REST API for Embedded R Execution, information about the Embedded R Execution scripts available, or the status or the result of an ansynchronous job. |
HEAD |
Retrieve header information about the Embedded R Execution operation. |
POST |
Execute the user-defined function in the Embedded R Execution script. |
Media Types
The REST API for Embedded R Execution supports the application/json
media
type.
Supported Headers
The REST API for Embedded R Execution supports the following headers that may be passed in the header section of the HTTP request or response.
Header | Description | Example |
Accept-Encoding |
List of acceptable encodings to support compression. | Accept-Encoding: gzip |
Content-Encoding |
List of acceptable encodings to support compression. | Content-Encoding: deflate |
Content-Type |
Media type of the body of the request. Required for POST and PUT requests. | Content-Type: application/json |