generated: '2026-09-02'
method: searched
source: 'The provider''s own getting-started manual (openapi/tietoevry-how-to-instruction.yaml, fetched from
  https://openbanking.api.tietoevry.com/documentation/how-to-instruction.yaml, HTTP 200, 2026-09-02), the
  version set published on the portal, and live probes of status.tietoevry.com and status.tieto.com'
versioning:
  scheme: 'Two-part. A path segment names the Berlin Group framework version (…/xs2a/v1.2/…, …/xs2a/v1.3/…,
    …/xs2a-premium/v1.3/…, …/xs2a-vam/v1.3/…), and the developer must ALSO pin an "API group version" on the
    registered application in the portal. The provider states: "Make sure you know the version of APIs that
    is chosen in the app you are going to use. It is important, because you will need to add it to every call
    you make on our APIs."'
  in: path
  versions_published:
  - '1.2'
  - '1.3'
  current: '1.3'
  document_versions:
    tieto-openbanking-xs2a: 1.3.4
    financial-api-aggregation: 1.0.0
    sepa-direct-debits: '1'
  environment_selector: 'The same path also selects the environment — {sandbox|live}. On the Swagger 2.0
    documents this is modelled as a path parameter literally named "sandbox|live" with an enum of sandbox and
    live; on the OpenAPI 3 documents it is two servers[] entries.'
  note: 'Both 1.2 and 1.3 remain published side by side. Nothing in the contracts or the portal states that
    1.2 is deprecated, states a date on which it stops, or marks any operation deprecated: true.'
deprecation:
  policy_published: false
  sunset_header: false
  deprecation_header: false
  deprecated_operations: 0
  evidence: 'No deprecation or sunset policy page exists on any of the three portals. No operation in the 211
    published operations carries deprecated: true, and no response declares a Sunset (RFC 8594) or Deprecation
    header. The only lifecycle signal a consumer gets is that an older path version stops appearing in the
    application version dropdown.'
sla:
  published: false
  evidence: 'No SLA, uptime commitment or support-response commitment is published on the public surface. The
    sandbox explicitly disclaims one: "The service has been built only as a demo preview. Its performance,
    availability and the data accuracy is not guaranteed and could vary over time and without notice."'
status_page:
  published: false
  evidence: 'Probed 2026-09-02: https://status.tietoevry.com/ and https://status.tieto.com/ neither resolve
    (no response). No status or incident-history link appears on api.tietoevry.com,
    openbanking.api.tietoevry.com, aggregation.api.tieto.com or credit.api.tietoevry.com.'
observed_degradation:
  - surface: openbanking.api.tietoevry.com content service
    observation: 'The developer portal''s own content backend returned HTTP 502 on every documentation
      endpoint probed on 2026-09-02 — /content-mgmt/content/documentation/get, /content/faq/get,
      /content/glossary/get and /content/solution/get. The single-page app that renders the documentation,
      FAQ and glossary pages reads from that service, so those pages had no content source at probe time.
      /notifications/get answered HTTP 400 with {"message":"Please contact administrator for detailed
      information about error"}. The static OpenAPI documents under /documentation/*.yaml were unaffected and
      all returned HTTP 200.'
  - surface: SEPA Direct Debits contact URL
    observation: 'info.contact.url in openapi/tietoevry-sepa-direct-debit-api-gateway.yaml points at
      https://tieto.ob5.konts.lv/documentation/payment-services/sepa-direct-debit/v1.0, an internal
      development host that does not respond. The published contract''s only documentation link is dead.'
brand_lifecycle:
  observation: 'The company itself is mid-rename. www.tietoevry.com now issues an HTTP 301 to
    https://www.tieto.com/en/, whose title is "We are Tieto"; the banking unit''s page has moved from
    /en/banking/ to /en/banktech/, and /en/banking/open-banking/ now redirects to the site root. The API
    hosts have not followed: the developer portals still live on api.tietoevry.com,
    openbanking.api.tietoevry.com and credit.api.tietoevry.com, while the aggregation portal and the live
    XS2A and payments gateways already sit on tieto.com (aggregation.api.tieto.com,
    openbanking.api.tieto.com, payments.api.tieto.com). Consumers therefore face a split-brand host set with
    no published migration note.'
  checked: '2026-09-02'