Open Bank solution - different error response format

Google Cloud Apigee
1

Hi Team,

We are using open bank solution for one of our PoC. While doing some testing I found that different errors are using different formats.

For Example:

  1. In Oauth proxy error response is in following format:
{
	"ErrorCode" : "invalid_request", 
	"Error" :"Invalid Authorization Code"
}
  1. In Accounts Service for invalid token the format is:
{
	"status": "error",
	"message": "Invalid Access Token"
}
  1. In Account service only for some other error the error format is:
{
	"error": "Unauthorized Transaction",
	"description": "Access Token does not contain an Account Number reference"
}

Just wanted to understand if there was any specific reason for doing so because if a developer wants to extract exact error message apart from reason phrase and status code then its difficult due to inconsistency of error formats across APIs. @sudharshan@apigee.com

2

Hi @Vipul Agarwal, Thanks for pointing this out. We are working on fixing this right now. Please expect to see an update on the GIT repo shortly. Thanks much once again !

3

Hi @Vipul Agarwal, This issue has been fixed and there is uniform error reponse across the openbank solution now.

The standard response is:

{
   "status": http_status_code,
   "message": "short_message",
   "description": "brief description about the error",
   "code": error_code_for_developer,
   "more_info": "link for more information on the error"
 }

This error response format will give a brief idea about what the error exactly is, and a link for developers which they can use for more information on the error generated.

Do let us know what are your impressions of this.