TietoEVRY · OpenAPI Overlay 1.0.0

API Evangelist enrichment overlay — Getting started!

2 actions 2 updates update extends ../openapi/tietoevry-how-to-instruction.yaml

Generated by API Evangelist Written by API Evangelist tooling for TietoEVRY's API. It is a proposal applied on top of the contract, not a document TietoEVRY publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-sourcex-apievangelist-harvestedx-apievangelist-providerx-apievangelist-http-statusx-authenticationx-idempotencyx-error-formatx-rate-limits

Targets 1

$.info

OpenAPI Overlay

overlay: 1.0.0
info:
  title: API Evangelist enrichment overlay — Getting started!
  version: 1.0.0
extends: ../openapi/tietoevry-how-to-instruction.yaml
x-generated: '2026-09-02'
x-method: generated
x-source: Generated by the API Evangelist enrichment pipeline from artifacts in this repository. It records our
  measurements ON TOP OF the provider contract and never mutates it.
actions:
- target: $.info
  description: Record API Evangelist provenance for this harvested contract.
  update:
    x-apievangelist-source: https://openbanking.api.tietoevry.com/documentation/how-to-instruction.yaml
    x-apievangelist-harvested: '2026-09-02'
    x-apievangelist-provider: tietoevry
    x-apievangelist-http-status: 200
- target: $.info
  description: State the runtime semantics the contract itself leaves unsaid, as measured by the enrichment pipeline.
  update:
    x-authentication: API key in the X-API-Key header, issued per application registered at https://openbanking.api.tietoevry.com.
      Live access additionally requires eIDAS QWAC/QSealC client certificates. See authentication/tietoevry-authentication.yml.
    x-idempotency: NOT SUPPORTED. X-Request-ID is a correlation identifier only; the provider documents no replay
      guarantee, no retention window and no Idempotency-Key header. Do not retry a write on timeout.
    x-error-format: 'Berlin Group envelope: { transactionStatus, tppMessages[{category,code,text}], psuMessage }.
      Not RFC 9457. See errors/tietoevry-problem-types.yml.'
    x-rate-limits: No platform rate limit is published. 429 fires when the consent frequencyPerDay quota set by
      the client is exhausted; no Retry-After or RateLimit-* header is returned. See rate-limits/tietoevry-rate-limits.yml.
    x-reversibility: Reversal operations exist (cancel / refund / reject / chargeback / recall / delete-consent)
      but NO time window is published for any of them. See conventions/tietoevry-conventions.yml.
    x-lifecycle: No deprecation or sunset policy, no status page, no dated changelog. See lifecycle/tietoevry-lifecycle.yml.