1. Developing Applications with Oracle Internet of Things Cloud Service
  2. Troubleshoot
  3. Troubleshoot REST API Issues

Troubleshoot REST API Issues

Use the information in this topic to resolve Oracle Internet of Things Cloud Service REST API known issues.

  • Issue:Oracle Internet of Things Cloud Service 16.1.5 does not return an appropriate message when you try to access any REST APIs that are no longer supported.

    Description: Several REST APIs that were available prior to the Oracle Internet of Things Cloud Service 16.1.5 release are no longer supported in the Oracle Internet of Things Cloud Service 16.1.5 version. When you try to access any of these unsupported REST APIs, Oracle Internet of Things Cloud Service returns a 404 (Not Found) status, but does not give information on what new APIs, if any, should be used.

    Workaround: Use the following table to get information about the REST APIs that are no longer supported in the Oracle Internet of Things Cloud Service 16.1.5 version and what the REST APIs, if any, that replaced them.
    REST APIs that are no longer supported in version 16.1.5 Replaced by the following REST APIs Notes
    /iot/api/v1/endpoints/{connector-endpoint-id} /iot/api/v2/apps/{app-id}/integrations See the latest REST API documentation.
    /iot/api/v1/endpoints/{configurations} None. Completely removed in version 16.1.5 of Oracle Internet of Things Cloud Service.
    /iot/api/v1/annotators None Completely removed in Oracle Internet of Things Cloud Service 16.1.5 version. When you’re configuring an integration in Oracle Internet of Things Cloud Service 16.1.5, the annotation references are explicitly defined.
    /iot/api/v1/formats /iot/api/v2/apps/{app-id}/formats Beginning with Oracle Internet of Things Cloud Service 16.1.5, you define message formats within the context of a device model.

  • Issue: A 403 Forbidden error is returned when a web application running on a particular host tries to call an Oracle Internet of Things Cloud Service REST API.

    Description: If a web application residing on a host tries to access an Oracle Internet of Things Cloud Service resource, then access is denied by default for a host that does not have a .oraclecloud.com or .oraclecloudapps.com domain suffix. You might notice the following error in the log file:

     <Error> <oracle.IoT.Security> <BEA-000000> <CORS : Invalid CORS request; Origin= ...

    This means that the host name has not been explicitly added to the CORS (Cross-Origin Resource Sharing) list. CORS specifies if the system that is hosting the web application is allowed to access Oracle Internet of Things Cloud Service resources.

    Workaround: You need to add the host name of the system hosting the web application to the CORS list. You can do this in the Allowed Hosts for Cross-Origin Resource Sharing field in the Security section of the Settings page of Oracle Internet of Things Cloud Service.