Send Requests

Use the following guidelines when sending requests for monitoring an Oracle Cloud service using the REST API.

URL Structure

To perform operations on an Oracle Cloud service resource by using REST API calls, you must specify the fully-qualified, unique URI of the resource.

The fully qualified URI of a resource is in the following format:

https://{api_endpoint}/{resource_base}/{resource_path}

• api_endpoint is the REST endpoint URL that you received when you subscribed to the service. For example, https://monitoring.{region}.oraclecloud.com

  where {region} is us, or europe for EMEA

• resource_base is the base URI of the resource. For example, /monitoring/{mydomain}/.customer/api

• resource_path is the path of a specific resource. For example, /v1/{resource}

Supported Methods

The following table describes the REST HTTP methods you can invoke for Oracle Cloud Service objects.

HTTP Method	Description
POST	Creates an object by using the JSON-formatted data in the request body.
GET	Retrieves information about the object/s specified in the request URI.
DELETE	Deletes the object specified in the request URI.

Each object for which you can perform API calls is identified uniquely by its URI.

Supported Headers

The REST API for monitoring Oracle Cloud services supports the following headers that may be passed in the header section of the HTTP request.

Header	Description	Example
Authorization:	Every HTTP request to the service should supply HTTP Basic Authentication credentials through the Authorization header. You can convert your user name and password to the Base64-encoded format by using standard tools, such as the base64 command on Linux hosts.	Authorization: Basic d2VibG9naWM6V2VsY29tZTE
X-ID-TENANT-NAME:	The http header X-ID-TENANT-NAME must be set to the identity domain ID where the user resides.	X-ID-TENANT-NAME: mydomain
Content-Type:	All the content in an HTTP request body sent to the API server must be encoded in JavaScript Object Notation (JSON).	Content-Type: application/json