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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Tietoevry

Tietoevry Financial API Aggregation

A single-integration aggregation layer over Nordic and Baltic banks, exposing provider discovery, end-user management and aggregated XS2A operations (accounts, balances, transactions, consents, confirmation of funds and payment initiation) across many connected ASPSPs behind one contract, with a pre-step SCA service and aggregated consent creation.

Documentation Provider Profile APIs.io OpenAPI GitHub

This API exposes 40 operations across 31 paths, organized into 8 resource areas, and defines 53 schemas. It is described by OpenAPI 2.0, at version 1.0.0.

Requests are made against the base URL https://aggregation.api.tieto.com.

40 operations 31 paths 53 schemas 4 DELETE22 GET2 OPTIONS11 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.0.0
Base URL
https://aggregation.api.tieto.com
Resource Areas
8

Paths & Operations 40

Across 31 paths, the API surfaces 40 operations — 4 DELETE, 22 GET, 2 OPTIONS, 11 POST, 1 PUT. They span 8 resource areas: Aggregated services, Pre-step SCA service, Provider information, End User management, Account Information Service, Account consent service, Confirmation of Funds Service, Payment Initiation Service. Each is listed below with its method, path, parameters, and response codes.

Aggregated services 5

Operations, which are executed for multiple destination providers.

POST
/v1/xs2a/v1.0/pre-auth
Initiate a Pre-step SCA, aggregated
aggregatedPreAuth 6 params → 201405500
OPTIONS
/v1/xs2a/v1.0/pre-auth
Check Pre-step SCA support, aggregated
aggregatedPreAuthOptions 4 params → 200500
GET
/v1/xs2a/v1.0/accounts
Retrieve aggregated List of Accounts
getAggregatedAccounts 5 params → 200
POST
/v1/xs2a/v1.0/consents
Establish Consent Transactions, aggregated
postAggregatedConsents 5 params → 200
GET
/v1/xs2a/v1.0/consents/creation-results/{correlation-id}
Fetch consent creation result
getAggregatedConsentCreationResult 5 params → 200
Pre-step SCA service 2

Operations for establishing Pre-step SCA

POST
/v1/xs2a/v1.0/providers/{provider-id}/pre-auth
Initiate a Pre-step SCA
preAuth 6 params → 201500
OPTIONS
/v1/xs2a/v1.0/providers/{provider-id}/pre-auth
Check, if Pre-step SCA is supported
preAuthOptions 5 params → 200500
Provider information 2

Retrieve information about providers.

GET
/v1/providers/v1.0/providers
Retrieve information on providers
getProviders 4 params → 200
GET
/v1/providers/v1.0/providers/{provider-id}
Retrieve information for a given provider
getProvider 4 params → 200
End User management 4

Operations for managing anonymous End Users.

POST
/v1/end-users/v1.0/end-users
Create an anonymous End User
createEndUser 3 params → 201
DELETE
/v1/end-users/v1.0/end-users/{end-user-id}
Delete the anonymous End User record
deleteEndUser 4 params → 200
GET
/v1/end-users/v1.0/end-users/{end-user-id}/providers
Retrieve the provider selection for an End User
getEndUserProviders 4 params → 200
PUT
/v1/end-users/v1.0/end-users/{end-user-id}/providers
Set the provider selection for an End User
setEndUserProviders 5 params → 200
Account Information Service 4

Operations for managing account information.

GET
/v1/xs2a/v1.0/providers/{provider-id}/accounts
Read Account List
getAccounts 7 params → 200400401403429
GET
/v1/xs2a/v1.0/providers/{provider-id}/accounts/{account-id}
Read Account Details
getAccount 8 params → 200400401403404429
GET
/v1/xs2a/v1.0/providers/{provider-id}/accounts/{account-id}/balances
Read Balance
getAccountBalances 7 params → 200400401403404429
GET
/v1/xs2a/v1.0/providers/{provider-id}/accounts/{account-id}/transactions
Read Transaction List
getAccountTransactions 11 params → 200400401403404429
Account consent service 7

Operations for establish and managing account information consent.

POST
/v1/xs2a/v1.0/providers/{provider-id}/consents
Establish Consent Transaction
postConsent 9 params → 200201400
GET
/v1/xs2a/v1.0/providers/{provider-id}/consents/{consent-id}
Get Consent Request
getConsent 6 params → 200400403
DELETE
/v1/xs2a/v1.0/providers/{provider-id}/consents/{consent-id}
Delete an Account Information Consent Object
deleteConsent 5 params → 204400404
GET
/v1/xs2a/v1.0/providers/{provider-id}/consents/{consent-id}/authorisations
Get authorisation sub-resources request
consentsGetAuthorizations 5 params → 200
POST
/v1/xs2a/v1.0/providers/{provider-id}/consents/{consent-id}/authorisations
Start authorisation process
consentsStartAuthorization 6 params → 200201
GET
/v1/xs2a/v1.0/providers/{provider-id}/consents/{consent-id}/authorisations/{authorisation-id}
Get SCA status request
consentsGetAuthorizationStatus 6 params → 200
GET
/v1/xs2a/v1.0/providers/{provider-id}/consents/{consent-id}/status
Get Status Request
getConsentStatus 6 params → 200400403
Confirmation of Funds Service 8

Operations for receiving funds confirmation.

POST
/v1/xs2a/v1.0/providers/{provider-id}/funds-confirmations
Confirmation of Funds Request
getFundsConfirmation 7 params → 200400
POST
/v1/xs2a/v1.0/providers/{provider-id}/funds-confirmation-consents
Establish Funds Confirmation Consent Transaction
postFundsConfirmationConsent 9 params → 200201400
GET
/v1/xs2a/v1.0/providers/{provider-id}/funds-confirmation-consents/{consent-id}
Get Funds Confirmation Consent Request
getFundsConfirmationConsent 6 params → 200400404
DELETE
/v1/xs2a/v1.0/providers/{provider-id}/funds-confirmation-consents/{consent-id}
Delete an Confirmation of Funds Service Object
deleteFundsConfirmationConsent 5 params → 204400404
GET
/v1/xs2a/v1.0/providers/{provider-id}/funds-confirmation-consents/{consent-id}/authorisations
Get authorisation sub-resources request
fundsConfirmationConsentsGetAuthorizations 5 params → 200
POST
/v1/xs2a/v1.0/providers/{provider-id}/funds-confirmation-consents/{consent-id}/authorisations
Start authorisation process
fundsConfirmationConsentsStartAuthorization 6 params → 200201
GET
/v1/xs2a/v1.0/providers/{provider-id}/funds-confirmation-consents/{consent-id}/authorisations/{authorisation-id}
Get SCA status request
fundsConfirmationConsentsGetAuthorizationStatus 6 params → 200
GET
/v1/xs2a/v1.0/providers/{provider-id}/funds-confirmation-consents/{consent-id}/status
Get Status Request
getFundsConfirmationConsentStatus 6 params → 200400404
Payment Initiation Service 8

Operations for payments.

GET
/v1/xs2a/v1.0/providers/{provider-id}/payments
Get Payment Products
getPaymentProducts 3 params → 200
GET
/v1/xs2a/v1.0/providers/{provider-id}/payments/{payment-product}/{payment-id}
Get Payment Details
getJSONPayment 6 params → 200
DELETE
/v1/xs2a/v1.0/providers/{provider-id}/payments/{payment-product}/{payment-id}
Payment cancellation for the specified product type and identifier
cancelPayment 10 params → 202204400404405
GET
/v1/xs2a/v1.0/providers/{provider-id}/payments/{payment-product}/{payment-id}/authorisations
Payment: Get authorisation sub-resources request
paymentsGetAuthorizations 6 params → 200
POST
/v1/xs2a/v1.0/providers/{provider-id}/payments/{payment-product}/{payment-id}/authorisations
Payment: Start authorisation process
paymentsStartAuthorization 9 params → 200201
GET
/v1/xs2a/v1.0/providers/{provider-id}/payments/{payment-product}/{payment-id}/authorisations/{authorisation-id}
Payment: Get SCA status request
paymentsGetAuthorizationStatus 7 params → 200
GET
/v1/xs2a/v1.0/providers/{provider-id}/payments/{payment-product}/{payment-id}/status
Payment: Get Status Request
getJSONPaymentStatus 7 params → 200400404
POST
/v1/xs2a/v1.0/providers/{provider-id}/payments/{payment-product}
Payment Initiation with JSON encoding of the Payment Instruction
initiateJSONPayment 11 params → 200201400404

Schemas 53

The contract defines 53 schemas that model the data the API accepts and returns. The most detailed are JsonLinks (16 properties), JsonAccountDetails (10 properties), JsonTransaction (9 properties), JsonGetPaymentResponse (9 properties). Each schema is shown below with its type and property counts.

JsonProvider
object
4 properties
JsonGetProviderResponse
object
1 property
JsonGetProvidersResponse
object
1 property
JsonCreateEndUserResponse
object
1 property
JsonProviderRef
object
2 properties
JsonPreAuthProviderResponse
object
2 properties
JsonPreAuthProvidersResponse
array
JsonGetEndUserProvidersResponse
object
1 property
JsonProviderId
object
1 property
JsonPutEndUserProvidersRequest
object
1 property
JsonAggregatedAccountAccess
object
3 properties
JsonAccountAccess
object
3 properties
JsonAccountDetails
object
JsonAccountDetails must contain one of iban, bban, maskedPan, msisdn or pan field
10 properties 1 required
JsonAccountReference
object
Must contain one of iban,bban,maskedPan,msisdn or pan field
6 properties 1 required
JsonAccountReport
object
3 properties 1 required
JsonAddress
object
5 properties 1 required
JsonAmount
object
2 properties 2 required
JsonBalance
object
4 properties 2 required
JsonErrorResponse
object
3 properties 1 required
JsonFundsConfirmationRequest
object
4 properties 2 required
JsonFundsConfirmationResponse
object
1 property 1 required
JsonGetAccountBalancesResponse
object
2 properties 1 required
JsonGetAccountResponse
object
1 property 1 required
JsonGetAccountTransactionsResponse
object
3 properties
JsonAccountList
object
2 properties
JsonGetAggregatedAccountsResponse
object
1 property 1 required
JsonGetAccountsResponse
object
1 property 1 required
JsonGetAuthorisationStatusResponse
object
1 property
JsonGetAuthorisationsResponse
object
1 property
JsonGetConsentResponse
object
7 properties 6 required
JsonNewConsentDetails
object
2 properties
JsonGetNewConsentDetails
object
2 properties
JsonAggregatedConsentCreationResultResponse
object
1 property 1 required
JsonAggregatedConsentsResponse
object
1 property 1 required
JsonAggregatedConsentCreation
object
A unified request for an aggregated creation of consents. Specific provider IDs shall be given.
6 properties 5 required
JsonGetConsentStatusResponse
object
1 property
JsonGetFundsConfirmationConsentResponse
object
6 properties 4 required
JsonGetPaymentProductsResponse
object
2 properties 1 required
JsonGetPaymentResponse
object
9 properties 5 required
JsonGetPaymentStatusResponse
object
2 properties 1 required
JsonHref
object
1 property
JsonLinks
object
16 properties
JsonMessage
object
4 properties 2 required
JsonPostAuthorisationsResponse
object
4 properties
JsonPostConsentsRequest
object
5 properties 5 required
JsonPostConsentsResponse
object
5 properties
JsonPostFundsConfirmationConsentsRequest
object
3 properties 3 required
JsonPostPaymentRequest
object
8 properties 5 required
JsonPostPaymentRequestWithIbanOrPan
object
8 properties 5 required
JsonPostPaymentResponse
object
7 properties 2 required
JsonPostPaymentResponseWithIbanOrPan
object
8 properties 2 required
JsonDeletePaymentResponse
object
2 properties
JsonTransaction
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tietoevry-financial-api-aggregation-swagger.json Raw ↑
#Aggregation#Open Banking#XS2A#Multibanking#Nordic#Baltic
← Back to T APIs
API Details
ID
tietoevry:tietoevry-financial-api-aggregation
Base URL
https://aggregation.api.tieto.com
Docs
https://aggregation.api.tieto.com/
Provider
Tietoevry
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=tietoevry-tietoevry-financial-api-aggregation&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/tietoevry-tietoevry-financial-api-aggregation"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Tietoevry Financial API Aggregation, 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.