Scenario: Sending Unstructured Data Using HTTPs

Optional. During the time it takes to create the domain, use the oci iot work-request get command and the required parameter to get the work request update for creating the domain. Replace the <work-request-id> with the work request id from the previous response:

oci iot work-request get --work-request-id <work-request-OCID>

The example response shows the create an IoT domain is accepted and in progress.

{
  "data": {
    "compartment-id": "<iot-domain-OCID>",
    "id": "<work-request-OCID>",
    "operation-type": "CREATE_IOT_DOMAIN",
    "percent-complete": 50.0,
    "resources": [
      {
        "action-type": "IN_PROGRESS",
        "entity-type": "iotDomain",
        "entity-uri": "/20250531/iotDomains/<iot-domain-OCID>",
        "identifier": "<iot-domain-OCID>",
        "metadata": null
      }
    ],
    "status": "ACCEPTED",
    "time-accepted": "2025-08-14T16:57:03.413000+00:00",
    "time-finished": null,
    "time-started": null,
    "time-updated": "2025-08-14T16:57:23.124000+00:00"
  },
  "etag": "<unique-id>"
}

oci iot work-request list-logs --work-request-id <work-request-OCID>

This example response shows the steps to create the IoT domain and that it's finishing:

{
  "data": {
    "items": [
      {
        "message": "Generating DNS record(s)",
        "timestamp": "2025-08-14T16:57:22.148000+00:00"
      },
      {
        "message": "Onboarding domain schema(s)",
        "timestamp": "2025-08-14T16:57:23.124000+00:00"
      },
      {
        "message": "Successfully onboarded domain schemas",
        "timestamp": "2025-08-14T16:58:43.508000+00:00"
      },
      {
        "message": "Finishing work request",
        "timestamp": "2025-08-14T16:58:43.771000+00:00"
      }
    ]
  }
}

Optional. During the time it takes to configure access to APEX, use the oci iot work-request get command and the required parameter to get the work request update. Replace the <work-request-id> with the work request id from the previous response:

oci iot work-request get --work-request-id <work-request-OCID>

Example response:

{
  "data": {
    "compartment-id": "<compartment-OCID>",
    "id": "<work-request-OCID>",
    "operation-type": "CONFIGURE_DOMAIN_DATA_ACCESS",
    "percent-complete": 0.0,
    "resources": [
      {
        "action-type": "IN_PROGRESS",
        "entity-type": "iotDomain",
        "entity-uri": "/20250531/iotDomains/<iot-domain-OCID>",
        "identifier": "<iot-domain-OCID>",
        "metadata": null
      }
    ],
    "status": "ACCEPTED",
    "time-accepted": "2025-08-14T17:44:44.716000+00:00",
    "time-finished": null,
    "time-started": null,
    "time-updated": "2025-08-14T17:44:44.716000+00:00"
  },
  "etag": "<unique-id>"
}

oci iot work-request list-logs --work-request-id <work-request-OCID>

This example response shows the access to APEX for the domain is in progress and that it's finishing:

{
  "data": {
    "items": [
      {
        "message": "Configuring domain data access is in Progress",
        "timestamp": "2025-08-14T17:45:19.708000+00:00"
      },
      {
        "message": "Finishing work request",
        "timestamp": "2025-08-14T17:45:19.978000+00:00"
      }
    ]
  }
}

oci iot work-request get --work-request-id <work-request-OCID>

This example response shows the configuring access to APEX for the IoT domain is updated:

"status": "SUCCEEDED"

{
  "data": {
    "compartment-id": "<compartment-OCID>",
    "id": "<work-request-OCID>",
    "operation-type": "CONFIGURE_DOMAIN_DATA_ACCESS",
    "percent-complete": 100.0,
    "resources": [
      {
        "action-type": "UPDATED",
        "entity-type": "iotDomain",
        "entity-uri": "/20250531/iotDomains/<iot-domain-OCID>",
        "identifier": "<iot-domain-OCID>",
        "metadata": null
      }
    ],
    "status": "SUCCEEDED",
    "time-accepted": "2025-08-14T17:44:44.716000+00:00",
    "time-finished": "2025-08-14T17:45:19.978000+00:00",
    "time-started": "2025-08-14T17:45:19.708000+00:00",
    "time-updated": "2025-08-14T17:45:19.978000+00:00"
  },
  "etag": "<unique-id>"
}