How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Aldermore Bank Standing Orders API

The Standing Orders API from Aldermore Bank — 2 operation(s) for standing orders.

Aldermore Bank Standing Orders API is one of 34 APIs that Aldermore Bank publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Standing Orders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 59 schemas. It is described by OpenAPI 3.2.0, at version 4.0.1.

Requests are made against a single base URL, /open-banking/v4.0/aisp.

2 operations 2 paths 59 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.0.1
Server
/open-banking/v4.0/aisp
Authentication
OAuth 2.0, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

Aldermore Bank Standing Orders API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (TPPOAuth2Security) using the clientCredentials flow, exposing 1 scope. It supports OAuth 2.0 (PSUOAuth2Security) using the authorizationCode flow, exposing 1 scope.

  • TPPOAuth2Security — TPP client credential authorisation flow with the ASPSP
  • PSUOAuth2Security — OAuth flow, it is required when the PSU needs to perform SCA with the ASPSP when a TPP wants to access an ASPSP resource owned by the PSU

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Standing Orders 2
GET
/accounts/{AccountId}/standing-orders
Get Standing Orders for an AccountId
GetAccountsAccountIdStandingOrders 7 params → 200400401403404405406429
GET
/standing-orders
Get Standing Orders
GetStandingOrders 6 params → 200400401403404405406429

Schemas 59

The contract defines 59 schemas that model the data the API accepts and returns. The most detailed are OBPostalAddress7 (18 properties), OBStandingOrder6 (15 properties), OBMandateRelatedInformation1 (8 properties), OBRemittanceInformationStructured (7 properties). Each schema is shown below with its type and property counts.

OBRemittanceInformationStructured
object
7 properties
OBProxy1
object
Specifies an alternate assumed name for the identification of the account.
3 properties 2 required
Room
string
Information that locates and identifies a room to form part of an address
OBFrequency6Code
string
For a full list of values see OBFrequency6Code in OBInternalCodeSet [here](https://github.com/OpenBankingUK/ExternalInternalCodeSets)
ExternalMandateStatus1Code
string
Specifies the status of the standing order in code form. For a full list of enumeration values refer to 'ExternalMandateStatus1Code' in ISOExternalCodeset [her…
Floor
string
Number that identifies the level within a building
OBActiveOrHistoricCurrencyAndAmount_4
object
The amount of the final Standing Order
2 properties 2 required
ExternalCreditorReferenceType1Code
string
Specifies the type of creditor reference as published in an external creditor reference type code set. For more information see ExternalCreditorReferenceType1C…
OBPostalAddress7
object
Information that locates and identifies a specific address, as defined by postal services.
18 properties
ExternalCategoryPurpose1Code
string
Enumeration of codes that outlines the type of purpose behind a transaction, payment or risk. For all enum values see ExternalCategoryPurpose1Code in ISOExtern…
BuildingNumber
string
Number that identifies the position of a building on a street.
Frequency_1
string
Individual Definitions: NotKnown - Not Known EvryDay - Every day EvryWorkgDay - Every working day IntrvlDay - An interval specified in number of calendar days…
Meta
object
Meta Data relevant to the payload
3 properties
PointInTime
string
Exact2NumericText - Further information on the exact point in time the event should take place. Specifies a frequency in terms of an exact point in time or mom…
OBReferredDocumentInformation
object
5 properties
Name_0
string
The account name is the name or names of the account owner(s) represented at an account level, as displayed by the ASPSP's online channels. Note, the account n…
OBExternalMandateClassification1Code
string
Type of mandate instruction. For a full list of values see OBExternalClassification1Code in OBInternalCodeSet [here](https://github.com/OpenBankingUK/ExternalI…
OBExternalStatusReason1Code
string
Low level textual error code, for all enum values see OBExternalStatusReason1Code in OBInternalCodeSet [here](https://github.com/OpenBankingUK/ExternalInternal…
OBBranchAndFinancialInstitutionIdentification5_1
object
Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on t…
5 properties 2 required
Identification_1
string
Unique and unambiguous identification of the servicing institution.
OBActiveOrHistoricCurrencyAndAmount_2
object
The amount of the first Standing Order
2 properties 2 required
LEI
string
Legal entity identification as an alternate identification for a party. Legal Entity Identifier is a code allocated to a party as described in ISO 17442 "Finan…
StandingOrderId
string
A unique and immutable identifier used to identify the standing order resource. This identifier has no meaning to the account owner.
Links
object
Links relevant to the payload
5 properties 1 required
OBInternalFinancialInstitutionIdentification4Code
string
Name of the identification scheme, in a coded form as published in an external list. For a full list of enumeration values refer to OBInternalFinancialInstitut…
OBFrequency6
object
Regularity with which credit transfer instructions are to be created and processed
3 properties 1 required
NextPaymentDateTime
string
The date on which the next payment for a Standing Order schedule will be made. All dates in the JSON payloads are represented in ISO 8601 date-time format. All…
NumberOfPayments
string
Number of the payments that will be made in completing this frequency sequence including any executed since the sequence start date.
OBError1
object
4 properties 1 required
StreetName
string
Name of a street or thoroughfare.
OBReadStandingOrder6
object
3 properties 1 required
OBActiveOrHistoricCurrencyAndAmount_3
object
The amount of the next Standing Order.
2 properties 2 required
OBActiveCurrencyAndAmount_SimpleType
string
A number of monetary units specified in an active currency where the unit of currency is explicit and compliant with ISO 4217.
OBStandingOrder6
object
15 properties 1 required
BuildingName
string
Name of a referenced building.
ISODateTime
string
All dates in the JSON payloads are represented in ISO 8601 date-time format. All date-time fields in responses must include the timezone. An example is below:…
TownName
string
Name of a built-up area, with defined boundaries, and a local government.
OBSupplementaryData1
object
Additional information that can not be captured in the structured fields and/or any other specific block.
Name_1
string
Name by which an agent is known and which is usually used to identify that agent.
OBErrorResponse1
object
An array of detail error codes, and messages, and URLs to documentation to help remediation.
4 properties 1 required
PostBox
string
Information that locates and identifies a box in a post office assigned to a person or organization, where letters for them are kept until called for.
SecondaryIdentification
string
This is secondary identification of the account, as assigned by the account servicing institution. This can be used by building societies to additionally ident…
CareOf
string
The 'care of' address is used whenever sending mail to a person or organisation who does not actually live or work at the address. They will receive the mail f…
Identification_3
string
Identification of the organisation issuing the invoice, when it is different from the creditor or ultimate creditor
DistrictName
string
Number that of the regional area, known as a district, which forms part of an address
PostCode
string
Identifier consisting of a group of letters and/or numbers that is added to a postal address to assist the sorting of mail.
AccountId
string
A unique and immutable identifier used to identify the account resource. This identifier has no meaning to the account owner.
Identification_4
string
Identification of the party to whom an invoice is issued, when it is different from the debtor or ultimate debtor.
UnitNumber
string
Number that identifies the unit of a specific address .
ExternalProxyAccountType1Code
string
Specifies the external proxy account type code, as published in the proxy account type external code set. For more information and a full list of values see Ex…
OBInternalAccountIdentification4Code
string
Name of the identification scheme, in a coded form as published in an external list. For a full list of enumeration values refer to OBInternalAccountIdentifica…
ExternalDocumentType1Code
string
Specifies the document type as published in an external document type code list. For more information see ExternalDocumentType1Code in ISOExternalCodeSet [here…
OBRemittanceInformation2
object
Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts' rec…
2 properties
ActiveOrHistoricCurrencyCode_1
string
A code allocated to a currency by a Maintenance Agency under an international identification scheme, as described in the latest edition of the international st…
OBMandateRelatedInformation1
object
Provides further details of the mandate signed between the creditor and the debtor.
8 properties 1 required
LastPaymentDateTime
string
The date on which the last (most recent) payment for a Standing Order schedule was made. All dates in the JSON payloads are represented in ISO 8601 date-time f…
OBActiveOrHistoricCurrencyAndAmount_11
object
The amount of the last (most recent) Standing Order instruction.
2 properties 2 required
OBAddressType2Code
string
Identifies the nature of the postal address. For a full set of codes see OBAddressType2Code in OBInternalCodeSet [here](https://github.com/OpenBankingUK/Extern…
OBCashAccount5_1
object
Provides the details to identify the beneficiary account.
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aldermore-standing-orders-api-openapi.yml Raw ↑

Other APIs Aldermore Bank publishes across the network.

Aldermore Bank Account Access Consents API
Aldermore Bank Accounts API
Aldermore Bank ATM API
Aldermore Bank Balances API
Aldermore Bank BCA API
Aldermore Bank Beneficiaries API
Aldermore Bank Branch API
Aldermore Bank CCC API
Aldermore Bank Direct Debits API
Aldermore Bank Domestic Payment Consents API
Aldermore Bank Domestic Payments API
Aldermore Bank Domestic Scheduled Payment Consents API
Where this information came from

This is an independent, third-party profile of Aldermore Bank Standing Orders API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.