Rule Evaluation - Error Scenarios

  • Updated

This document describes the HTTP response error codes you might get when making a rule evaluation request.

The sections below describe each of the codes and how you can solve them.

 

HTTP Response Code 400

If your request returns with HTTP error code 400, and response body, this means the request is malformed. Make sure the request structure follows the swagger definition of the v3 rule-engine API.

 

HTTP Response Code 401

If your request returns without body, and you get the HTTP error code 401, you need to retrieve a valid access token from https://auth.apiax.io/auth/realms/apiax/protocol/openid-connect/token and use it as an Authentication Bearer token

 

HTTP Response Code 404

If your request returns with a JSON structure in the response body, and you get the HTTP error code 404, this means the URL used for the request is malformed. For example:


{"timestamp":1630591806028,"status":404,"error":"Not Found","path":"/XX/api/v3/rules/inspect"}

You need to change the URL for pointing to the correct location: /api/v3/rules/inspect or /api/v3/rules/eval

 

HTTP Response Code 502

If the service does not respond or you get a "Bad Gateway” message in the response body, this means the service is down. Get more information at https://status.apiax.io or contact support@apiax.com

 

HTTP Response Code 503

If your request returns with a JSON structure in the response body, and you get the HTTP error code 503, this means an unknown error occurred while evaluating the request.

 

Related documents

Refer to the following documents for additional information and details about Rule Evaluation.

 

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.

Still have questions?

Please submit a request and we will get back to you shortly.

Submit a request