We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In the case of account information multiple Content Type is supported:
"content": { "application/json; charset=utf-8": { "schema": { "$ref": "#/components/schemas/OBReadConsentResponse1" } }, "application/json": { "schema": { "$ref": "#/components/schemas/OBReadConsentResponse1" } }, "application/jose+jwe": { "schema": { "$ref": "#/components/schemas/OBReadConsentResponse1" } } }
While in case of Confirmation of funds only "application/json; charset=utf-8" is supported.
"content": { "application/json; charset=utf-8": { "schema": { "$ref": "#/components/schemas/OBFundsConfirmationConsentResponse1" } } }
This is inconsistent and also API Gateway might not support charset encoding validation breaking the specification validation
Can this be made consistent as in case of Account Information Specification
The text was updated successfully, but these errors were encountered:
Specification 3.1.8
Sorry, something went wrong.
No branches or pull requests
In the case of account information multiple Content Type is supported:
While in case of Confirmation of funds only "application/json; charset=utf-8" is supported.
This is inconsistent and also API Gateway might not support charset encoding validation breaking the specification validation
Can this be made consistent as in case of Account Information Specification
The text was updated successfully, but these errors were encountered: