Page History

...

In these cases it is most likely a configuration issue. The web server might not be routing the request to the OECGI properly. Go back through the Server Preparation steps. The URL Rewrite Rules can easily fail with just one minor typo.

API Generated

When Generally there are two reasons why the HTTP Framework is unable to process the URI request, it will return a message like this::would return a 404 response. The usual scenario is that the resource hasn't been defined in the Resource Manager yet. In these cases, the API will return this message:

GET https://www.examples.org/parts

{
    "type": "about:blank",
    "title": "Not Found",
    "status": 404,
    "detail": "This is not a valid web API endpoint."
}

However, it is still possible to get a 404 response even if your resource has been defined. This can happen if the URI includes query params that are not defined as a part of the resource.

GET https://www.examples.org/parts

Here are a few reasons and symptoms.

Resource endpoint is not defined in the Resource Manager.

This most likely means you forgot to select at least one HTTP method:

...