generated: '2026-09-05'
method: searched
source: Probed developer.citi.com/apidocs/{changelog,release-notes,whats-new}, partner.citi.com/changelog, and searched
  the full 504-URL Docusaurus sitemap at https://developer.citi.com/apidocs/sitemap.xml on 2026-09-05.
published: false
entry_count: 0
note: 'Citi publishes NO dated changelog, release notes page or "what is new" feed for its API estate. The sitemap
  for the institutional documentation site contains 504 URLs and not one of them matches changelog, release, whats-new
  or new-features. Every candidate path probed returned 404. This is a real gap: an integrator cannot tell from
  any public source when a Citi contract last changed or what changed in it.'
what_exists_instead:
  versioned_contracts: Version is expressed by publishing a new contract at a new path rather than by logging a
    change. Concurrent major versions currently published side by side include Authentication V1-V4, Account Services
    v4 and v5, WorldLink V1/V2.4/V3.3/V5.1, Statements v1 and v2, VCA lifecycle v1 and 2.0.0, and e-Mandate v1 and
    v2.
  deprecation_headers: Three contracts declare RFC 8594 Deprecation, Sunset and Link response headers, which is
    a runtime change signal rather than a published log. See lifecycle/citi-lifecycle.yml.
  spec_versions: Each OpenAPI carries an info.version (for example Payment Refund 2.0.0, Proof of Payment 1.0.0,
    VCA Life Cycle Management 2.0.0). Diffing the harvested contracts in openapi/ against a future harvest is currently
    the only way to detect change.
probed:
- url: https://developer.citi.com/apidocs/changelog
  status: 404
- url: https://developer.citi.com/apidocs/release-notes
  status: 404
- url: https://developer.citi.com/apidocs/whats-new
  status: 404
- url: https://partner.citi.com/changelog
  status: 404
- url: https://developer.citi.com/apidocs/sitemap.xml
  status: 200
  note: 504 URLs, zero changelog-shaped entries
entries: []