Using the OCI API to send REST calls for managing OCI

OCI has taken an API-first strategy, which means that before they develop their UIs, they develop the API that will interact with the backend resources. The OCI APIs are typical REST APIs, meaning they use the standard HTTPS requests and responses.

Every OCI service has its own API endpoint. To check the current endpoint related to the specific region you want to send the call to, refer to https://docs.oracle.com/en-us/iaas/api/.

OCI maintains its own API versioning as well. If you look carefully at the endpoint, then you will find the desired API version from the base path of the API endpoint. For example, as of now, most of the APIs are versioned as 20160918.

Here's an example for a GET request to list users in the Phoenix region:

GET https://identity.us-phoenix1.oraclecloud.com/20160918/users

For tighter security, all OCI API requests must be signed for authentication purposes. For more details on the signature...