Release 3.6.0 - Accounts API schema version via Accept header + Issuing surface alignment

[david-ruiz-cko]

*** BREAKING CHANGES ***

This release introduces a shared internal helper for setting the Accounts API schema-version Accept header and updates the Platforms API to consistently include this header in all relevant /accounts/entities operations. It also adds comprehensive tests to ensure the correct Accept header is sent by default and when overridden, and updates test fixtures to the latest v3.0 schema.

Accounts API Accept Header Handling:

• Added a new internal helper function getConfigWithAcceptHeader in accept-header.js to construct request configs with the correct schema-version Accept header for /accounts/entities endpoints.
• Refactored subentity.js and entity-requirements.js to use the shared getConfigWithAcceptHeader, ensuring all entity-related requests send the correct Accept header. [1] [2]
• Updated getEntityRequirements in entity-requirements.js and its usage in platforms.js to accept an optional schemaVersion parameter, defaulting to '3.0'. [1] [2]

Testing and Schema Updates:

• Added a new test suite accept-header-unit.js to verify that all entity operations send the correct Accept header by default and when an explicit schema version is provided.
• Updated test fixtures in subentity-unit.js to use the v3.0 schema, including nested individual objects for representatives, new company and processing details fields, and updated contact details. [1] [2] [3] [4] [5] [6] [7] [8]

---

An also this release aligns the Issuing surface with the 2026-06-29 API spec. The Node SDK is untyped (all bodies are plain object), so only client-method-level changes apply — field/schema changes flow through the object bodies unchanged.

Disputes

• Add amendDispute(disputeId, body) — POST /issuing/disputes/{disputeId}/amend (new, non-deprecated). Body supports reason, amount, evidence, fraud_details, reason_change_justification, action_response.
• escalateDispute now accepts an optional body (for fraud_details).
• Correct submitDispute — the spec keeps POST /issuing/disputes/{disputeId}/submit present with deprecated: true. It was previously (incorrectly) documented as removed / returns 404 on 2026-04-15. Now marked deprecated-but-present, message points at create / amend, and it accepts an optional body. Its existing test stays.

Cards (⚠️ breaking)

• Remove scheduleCardRevocation and cancelScheduledCardRevocation — POST/DELETE /issuing/cards/{cardId}/schedule-revocation were removed from the API. Revocation scheduling is now expressed via the update-card request's revocation_date.

Other

• Updated .d.ts declarations for all touched methods.
• Removed the 4 schedule-revocation unit tests; added an amendDispute unit test (all 6 fields incl. action_response) and enriched the escalate test with fraud_details.

Testing

Full suite: 845 passing, 0 failing, 84 pending (npm test). No lingering schedule-revocation references in src/test/types.

Breaking changes for release notes

• Removal of scheduleCardRevocation / cancelScheduledCardRevocation.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud