Retail FAQs

How do I deregister one of my apps or delete my account from the Developer Portal?

You can deregister an app, or your entire account, by getting in touch with our team through our Support page. We'll let you know once we've done it.

What APIs are available in live and the Sandbox?

Below is a list of the APIs and versions available in live and the Sandbox

API Live Sandbox
AIS
POST /account-requests v1.1, v2 N/A
DELETE /account-requests/{AccountRequestID} v1.1, v2 N/A
GET /account-requests/{AccountRequestId} v2 N/A
GET /accounts v1.1, v2, v3, v3.1       v3.1
GET /accounts/{AccountID} v1.1, v2, v3, v3.1 v3.1
GET /accounts/{AccountID}/balances v1.1, v2, v3, v3.1 v3.1
GET /accounts/{AccountID}/beneficiaries v1.1, v2, v3, v3.1 v3.1
GET /accounts/{AccountID}/direct-debits v1.1, v2, v3, v3.1 v3.1
GET /accounts/{AccountID}/scheduled-payments v1.1, v2, v3, v3.1 v3.1
GET /accounts/{AccountID}/standing-orders v1.1, v2, v3, v3.1 v3.1
GET /accounts/{AccountID}/transactions v1.1, v2, v3, v3.1 v3.1
GET /accounts/{AccountID}/product v1.1, v2, v3, v3.1 v3.1
DELETE /account-access-consents/{ConsentId} v3, v3.1 v3.1
POST /account-access-consents v3, v3.1 v3.1
GET /account-access-consents/{ConsentId} v3, v3.1 v3.1
GET /accounts/{AccountId}/statements N/A v3.1
GET /accounts/{AccountId}/statements/{StatementId}/file N/A v3.1
GET /accounts/{AccountId}/offers v3.1 v3.1
PIS
POST /payments v1.1 N/A
POST /payments-submission v1.1 N/A
GET /payment-submissions/{PaymentSubmissionId} v1.1 N/A
POST /domestic-payment-consents v3, v3.1 v3.1
GET /domestic-payment-consents/{ConsentId} v3, v3.1 v3.1
POST /domestic-payments v3, v3.1 v3.1
GET /domestic-payments/{DomesticPaymentId} v3, v3.1 v3.1
POST /domestic-scheduled-payment-consents v3, v3.1 v3.1
GET /domestic-scheduled-payment-consents/{ConsentId} v3, v3.1 v3.1
POST /domestic-scheduled-payments v3, v3.1 v3.1
GET /domestic-scheduled-payments/{DomesticScheduledPaymentId} v3, v3.1 v3.1
POST /domestic-standing-order-consents v3, v3.1 v3.1
GET /domestic-standing-order-consents/{ConsentId} v3, v3.1 v3.1
POST /domestic-standing-orders v3, v3.1 v3.1
GET /domestic-standing-orders/{DomesticStandingOrderId} v3, v3.1 v3.1
GET /domestic-payment-consents/{ConsentId}/fundconfirmation v3.1 v3.1
CBPII
POST /funds-confirmation-consents v3.1 v3.1
GET /funds-confirmation-consents/{ConsentId} v3.1 v3.1
POST /funds-confirmations v3.1 v3.1
DELETE /funds-confirmation-consents/{ConsentId} v3.1 v3.1
Open Data
ATM v2.2 N/A
Branch v2.2 N/A
Personal Current Accounts v2.2 N/A
Service Quality Metrix v1 N/A

The following utility APIs are versionless and are available in both the live environment and Sandbox; GET /.wellknown; GET /authorize; POST /register; POST /token 

What do the following exception codes relate to?

APIs for version 3 now return granular error codes. All previous APIs return standard HTTP codes. The HTTP codes used within Nationwide Open Banking APIs are:

  • 400 (Bad Request) 
  • 401 (Unauthenticated/Unauthorised)
  • 404 (Not Found)
  • 403 (Forbidden)
  • 429 (Too Many Requests)
  • 500 (Internal Server Error)
  • 503 (Services unavailable or too busy)

For more details, refer to the detailed API specifications available on the central industry Open Banking website.