feature/INT-1661 - Accounts API schema version via Accept header + Issuing surface alignment - #438
Merged
Merged
Conversation
Align the Issuing surface with the 2026-06-29 API spec.
Disputes:
- Add amendDispute(disputeId, body) (POST /issuing/disputes/{id}/amend)
- escalateDispute now accepts an optional body (fraud_details)
- Correct submitDispute: the spec keeps it present with deprecated: true
(it was wrongly documented as removed / returning 404). Refresh the
deprecation message to point at createDispute / amendDispute; it now
accepts an optional body.
Cards (BREAKING):
- Remove scheduleCardRevocation and cancelScheduledCardRevocation; the
POST/DELETE /issuing/cards/{id}/schedule-revocation endpoints were
removed from the API. Revocation scheduling is now expressed via the
update-card request's revocation_date.
Updates the .d.ts declarations and unit tests accordingly.
Full suite: 845 passing, 0 failing, 84 pending.
armando-rodriguez-cko
previously approved these changes
Jul 22, 2026
… into feature/INT-1661
|
armando-rodriguez-cko
approved these changes
Jul 22, 2026
david-ruiz-cko
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request 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/entitiesoperations. 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:
getConfigWithAcceptHeaderinaccept-header.jsto construct request configs with the correct schema-version Accept header for/accounts/entitiesendpoints.subentity.jsandentity-requirements.jsto use the sharedgetConfigWithAcceptHeader, ensuring all entity-related requests send the correct Accept header. [1] [2]getEntityRequirementsinentity-requirements.jsand its usage inplatforms.jsto accept an optionalschemaVersionparameter, defaulting to '3.0'. [1] [2]Testing and Schema Updates:
accept-header-unit.jsto verify that all entity operations send the correct Accept header by default and when an explicit schema version is provided.subentity-unit.jsto use the v3.0 schema, including nestedindividualobjects for representatives, new company and processing details fields, and updated contact details. [1] [2] [3] [4] [5] [6] [7] [8]An also this pull request 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
amendDispute(disputeId, body)—POST /issuing/disputes/{disputeId}/amend(new, non-deprecated). Body supportsreason,amount,evidence,fraud_details,reason_change_justification,action_response.escalateDisputenow accepts an optionalbody(forfraud_details).submitDispute— the spec keepsPOST /issuing/disputes/{disputeId}/submitpresent withdeprecated: 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)
scheduleCardRevocationandcancelScheduledCardRevocation—POST/DELETE /issuing/cards/{cardId}/schedule-revocationwere removed from the API. Revocation scheduling is now expressed via the update-card request'srevocation_date.Other
.d.tsdeclarations for all touched methods.amendDisputeunit test (all 6 fields incl.action_response) and enriched the escalate test withfraud_details.Testing
Full suite: 845 passing, 0 failing, 84 pending (
npm test). No lingeringschedule-revocationreferences insrc/test/types.Breaking changes for release notes
scheduleCardRevocation/cancelScheduledCardRevocation.