The first custom component of the resource URI can be an app name, e.g., /api/v1/<app>/<resource>. This app component helps the API service to find the corresponding controller for processing the request.

Most resource URIs are mapped to app-less URIs like /api/v1/<resources>, so the app name can be unavailable.


  • The API service was not able to recognize the resource URI and the first custom component of the URI does not look to be a valid app name
  • No custom components were specified in the resource URI


  • Check if the resource URI was properly specified


    "status": 400,
    "errors": [
            "code": "APP_NOT_FOUND",
            "message": "Invalid app component in URL or app is not installed",
            "more_info": ""