End-to-End Example

End-to-End Example integration on the QodexAI API Network: This public API documentation features ready-to-use APIs, Collections, and more from Oracle Developers.

End-to-End Example | OCI NoSQL Playground Workspace | API documentation

postman_colls

A token that uniquely identifies a request so it can be retried
in case of a timeout or server error without risk of executing
that same action again. Retry tokens expire after 24 hours, but
can be invalidated before then due to conflicting
operations. For example, if a resource has been deleted and
purged from the system, then a retry of the original creation
request might be rejected.


opc-retry-token

opc-request-id

Content-Type

Accept

1.1. Create a new table.

1.1. Create a new table. 1. Create a table End-to-End Example integration on the QodexAI API Network: This public API documentation features ready-to-use APIs, Collections, and more from Oracle Developers.

1.1. Create a new table. 1. Create a table End-to-End Example | OCI NoSQL Playground Workspace | API documentation

1. Create a table

1. Create a table End-to-End Example integration on the QodexAI API Network: This public API documentation features ready-to-use APIs, Collections, and more from Oracle Developers.

1. Create a table End-to-End Example | OCI NoSQL Playground Workspace | API documentation

<h1>Oracle Cloud Infrastructure (OCI) NoSQL Playground</h1>

<p>Using the OCI Console just to get your credentials, you can do everything using just APIs.</p>

<h2>Using the Collections to make API calls</h2>

<h3>Get OCI Credentials</h3>

<ul>
<li><strong>tenancy_ocid</strong>: OCID of your tenancy.<br>
To get the value, see <a href="https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#Required_Keys_and_OCIDs">Required Keys and OCIDs</a>.<br>
Example: <code>ocid1.tenancy.oc1..</code> (shortened for brevity)</li>
<li><strong>user_ocid</strong>: OCID of the user calling the API.<br>
To get the value, see <a href="https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#Required_Keys_and_OCIDs">Required Keys and OCIDs</a>.<br>
Example: <code>ocid1.user.oc1..</code></li>
<li><strong>fingerprint</strong>: Fingerprint for the public key that was added to this user.<br>
To get the value, see <a href="https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#Required_Keys_and_OCIDs">Required Keys and OCIDs</a>.</li>
<li><strong>private_key</strong>: Contents of the private key file.<br>
You can open the file in an editor and copy the contents or use a command like <code>pbcopy &lt; ~/.oci/oci_api_key.pem</code><br>
The key pair must be in PEM format. For instructions on generating a key pair in PEM format, see <a href="https://docs.oracle.com/en-us/iaas/Content/API/Concepts/apisigningkey.htm#Required_Keys_and_OCIDs">Required Keys and OCIDs</a>.</li>
<li><strong>passphrase</strong>: Passphrase used for the key. Only required if it key is encrypted.</li>
<li><strong>region</strong>: An Oracle Cloud Infrastructure region. See <a href="https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm#top">Regions and Availability Domains</a>.<br>
Example: <code>us-ashburn-1</code></li>
<li><strong>compartment_ocid</strong>: OCID of the compartment that will be used for the API calls.</li>
</ul>

<h3>Fork, Select and Update OCI Credentials Environment</h3>

<p>Fork and Update the <code>OCI Credentials</code> Qodex Environment Variables with your Oracle Cloud Infrastructure credentials information.</p>

<p><img src="https://github.com/junior/Qodex_oracle_cloud_oci/raw/main/images/Qodex_oci_credentials.gif" alt=""></p>


OCI NoSQL Playground

Github

Twitter

Developer Website

OCI NoSQL Playground projects on the QodexAI API Network: This public API documentation features ready-to-use APIs, Collections, and more from Oracle Developers.

Key	Datatype	Required	Description
opc-retry-token	string		A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.
opc-request-id	string		The client request ID for tracing.
Content-Type	string
Accept	string