eric yu Posted July 18 Share Posted July 18 Using the authorisationId provided from the GET /auth call to the provider, I tried to make the call to PATCH /authorisations with the following body. This consistently gives me 403 Forbidden: { "data":{ "status":"success", "bankAccounts":[ { "bankAccountExternalId":"string1234", "accountName":"string", "bankIdentifier":"1234", "branchIdentifier":"string", "accountIdentifier":"13425" }, { "bankAccountExternalId":"string4321", "accountName":"string", "bankIdentifier":"4321", "branchIdentifier":"string", "accountIdentifier":"14253" } ] } } Link to comment Share on other sites More sharing options...
Jordan Hall Posted September 12 Share Posted September 12 Morning @eric yu. Did you manage to get this resolved? 403 forbiddens can occur if your passing an incorrect authorisation ID into the query params of the request, also ensure you are using the correct base URL as documented on the Banking Service developer portal. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now