[OBIE-794] AIB - Bad request - request param has invalid date format - JIRA

AIB - Bad request - request param has invalid date format

Description

An example of the error we are seeing:

GET https://apis.aibgb.co.uk/api/open-banking/v2.0/accounts/23858602282265/transactions?fromBookingDateTime=2019-06-01T00:00:00
Request header:
Authorization: Bearer xxxxx
Accept: application/json x-fapi-financial-id: 0015800000jf9VgAAI

Response:
Http response code: 400

Response header:
Date: Fri, 30 Aug 2019 12:20:14 GMT Transfer-Encoding: chunked Connection: keep-alive X-Application-Context: msf-edge-server:https,prod:9006 Access-Control-Allow-Headers: origin, x-requested-with, accept X-Frame-Options: SAMEORIGIN Access-Control-Allow-Methods: GET, PUT, POST, DELETE, PATCH Pragma: no-cache Strict-Transport-Security: max-age=31536000 Access-Control-Allow-Origin: * Access-Control-Max-Age: 3628800 X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: no-store, must-revalidate, no-cache, max-age=0 X-Permitted-Cross-Domain-Policies: none Content-Security-Policy: self

Response body:
{"timestamp":1567167613814,"status":400,"code":"400-9000-1015","uuid":"85972a3b243767ab","error":"Bad Request","message":"Request param has invalid date format"}

The data format we are supplying is correct as per the https://openbanking.atlassian.net/wiki/spaces/DZ/pages/126485500/Transactions+v2.0.0 spec

Technical Impact

None

Workaround

None

Resolution Notes

None

Impact Assessment

None

Status

Assignee

Unassigned

Reporter

Beejal Nagar

Reference

None

Service Desk Reference

OBSD-10618

ASPSP

Query Type

None

TPP Impact

High

TPP

OB Environment

Production

Business Impact Severity

None

Share

Yes