API release notes October 2026
This changelog lists all API changes released in October 2026, grouped by product area. Each section can be expanded to view breaking changes, new endpoints, and other updates for that area. Review the Breaking Changes entries carefully, as these may require updates to your integration.
PaymentsLD
Payments Integration
BreakingBreaking Changes
| Endpoint | Change | Impact | Migration |
|---|---|---|---|
| POST/payments/integration/v1/spaces/{spaceId}/payments | Removed the changeNotificationUrl request property. | Client payloads including the changeNotificationUrl field will be rejected. | Remove the changeNotificationUrl parameter from request payload models. |
Modified the strict schema constraint min at payments/amount/value in the request payload. | Payloads violating the updated min validation rule will be rejected. | Update client-side schema definitions to respect the new min constraint. | |
Modified the strict schema constraint max at payments/amount/value in the request payload. | Payloads violating the updated max validation rule will be rejected. | Update client-side schema definitions to respect the new max constraint. | |
Removed the payments/creditor/address request property. | Client payloads including the payments/creditor/address field will be rejected. | Remove the payments/creditor/address parameter from request payload models. | |
Removed the payments/creditor/verificationId request property. | Client payloads including the payments/creditor/verificationId field will be rejected. | Remove the payments/creditor/verificationId parameter from request payload models. | |
Removed the payments/creditor/account/parent request property. | Client payloads including the payments/creditor/account/parent field will be rejected. | Remove the payments/creditor/account/parent parameter from request payload models. | |
Modified the strict schema constraint minLength at payments/creditor/account/bank/identifier in the request payload. | Payloads violating the updated minLength validation rule will be rejected. | Update client-side schema definitions to respect the new minLength constraint. | |
Removed the THIRD_PARTY enum value from the payments/creditor/account/bank/scheme request property. | Submitting THIRD_PARTY will result in schema validation failures. | Remove usage of THIRD_PARTY and implement fallback logic. | |
Modified the strict schema constraint minLength at payments/creditor/account/identifier in the request payload. | Payloads violating the updated minLength validation rule will be rejected. | Update client-side schema definitions to respect the new minLength constraint. | |
Modified the strict schema constraint minLength at payments/reference/value in the request payload. | |||
Modified the strict schema constraint minItems at payments in the request payload. | Payloads violating the updated minItems validation rule will be rejected. | Update client-side schema definitions to respect the new minItems constraint. | |
| POST/payments/integration/v1/spaces/{spaceId}/payments/transfers | Removed the changeNotificationUrl request property. | Client payloads including the changeNotificationUrl field will be rejected. | Remove the changeNotificationUrl parameter from request payload models. |
Modified the strict schema constraint min at payment/amount/value in the request payload. | Payloads violating the updated min validation rule will be rejected. | Update client-side schema definitions to respect the new min constraint. | |
Modified the strict schema constraint max at payment/amount/value in the request payload. | Payloads violating the updated max validation rule will be rejected. | Update client-side schema definitions to respect the new max constraint. | |
Removed the payment/creditor/verificationId request property. | Client payloads including the payment/creditor/verificationId field will be rejected. | Remove the payment/creditor/verificationId parameter from request payload models. | |
Modified the strict schema constraint minLength at payment/reference/value in the request payload. | Payloads violating the updated minLength validation rule will be rejected. | Update client-side schema definitions to respect the new minLength constraint. | |
| GET/payments/integration/v1/spaces/{spaceId}/payments/{paymentId} | Removed the counterParty response property under status 200. | Client payloads including the counterParty field will be rejected. | Remove the counterParty parameter from response payload under status 200 models. |
Removed the originatingAccount response property under status 200. | Client payloads including the originatingAccount field will be rejected. | Remove the originatingAccount parameter from response payload under status 200 models. | |
Removed the type response property under status 200. | Client payloads including the type field will be rejected. | Remove the type parameter from response payload under status 200 models. | |
Removed the availableOperations response property under status 200. | Client payloads including the availableOperations field will be rejected. | Remove the availableOperations parameter from response payload under status 200 models. | |
Removed the createdAt response property under status 200. | Client payloads including the createdAt field will be rejected. | Remove the createdAt parameter from response payload under status 200 models. | |
Removed the endToEndId response property under status 200. | Client payloads including the endToEndId field will be rejected. | Remove the endToEndId parameter from response payload under status 200 models. | |
Removed the reference response property under status 200. | Client payloads including the reference field will be rejected. | Remove the reference parameter from response payload under status 200 models. | |
Modified the strict schema constraint min at amount/value in the response payload under status 200. | Payloads violating the updated min validation rule will be rejected. | Update client-side schema definitions to respect the new min constraint. | |
Modified the strict schema constraint max at amount/value in the response payload under status 200. | Payloads violating the updated max validation rule will be rejected. | Update client-side schema definitions to respect the new max constraint. |
InfoImprovements (Non-Breaking)
| Endpoint | Details | Impact |
|---|---|---|
| POST/payments/integration/v1/spaces/{spaceId}/payments | Updated the schema metadata description at locale in the request payload. | Provides clearer guidance when using this property. |
Updated the schema metadata example at locale in the request payload. | ||
Updated the schema metadata description at payments/amount/value in the request payload. | ||
Added the new IBAN enum value to the payments/creditor/account/scheme request property. | You can now use this new enum value in requests. | |
Added the new BBAN enum value to the payments/creditor/account/scheme request property. | ||
Added the new ANB enum value to the payments/creditor/account/scheme request property. | ||
Added the new SE_BANKGIRO enum value to the payments/creditor/account/scheme request property. | ||
Added the new SE_PLUSGIRO enum value to the payments/creditor/account/scheme request property. | ||
Updated the schema metadata description at payments/creditor/account in the request payload. | Provides clearer guidance when using this property. | |
Updated the schema metadata description at payments/creditor/name in the request payload. | ||
| POST/payments/integration/v1/spaces/{spaceId}/payments/transfers | Updated the schema metadata description at locale in the request payload. | Provides clearer guidance when using this property. |
Updated the schema metadata example at locale in the request payload. | ||
Updated the schema metadata description at payment/amount/value in the request payload. | ||
The locale property is no longer required in the request payload. | Clients can omit this property. | |
| GET/payments/integration/v1/spaces/{spaceId}/payments/{paymentId} | Updated the schema metadata description at amount/value in the response payload under status 200. | Provides clearer guidance when using this property. |
The availableOperations property is no longer required in the response payload under status 200. | Clients can omit this property. | |
The type property is no longer required in the response payload under status 200. | ||
Updated the schema metadata description in the response payload under status 200. | Provides clearer guidance when using this property. |
Payments Reconciliation
BreakingBreaking Changes
| Endpoint | Change | Impact | Migration |
|---|---|---|---|
| GET/payments/reconciliation/documents/v1/spaces/{spaceId}/documents/aggregations | Modified the strict schema constraint oneOf at */*/documentAggregations/aggregations/modifier in the response payload under status 200. | Payloads violating the updated oneOf validation rule will be rejected. | Update client-side schema definitions to respect the new oneOf constraint. |
Modified the strict schema constraint oneOf at */*/documentAggregations/aggregations/modifier in the response payload under status 400. | |||
| GET/payments/reconciliation/documents/v1/spaces/{spaceId}/documents/{documentId}/aggregations | Modified the strict schema constraint oneOf at */*/documentAggregations/aggregations/modifier in the response payload under status 200. | Payloads violating the updated oneOf validation rule will be rejected. | Update client-side schema definitions to respect the new oneOf constraint. |
Modified the strict schema constraint oneOf at */*/documentAggregations/aggregations/modifier in the response payload under status 400. | |||
| POST/payments/reconciliation/documents/v1/spaces/{spaceId}/documents/{documentId}:findProposedModifiers | Modified the strict schema constraint oneOf at */*/modifier in the response payload under status 200. | Payloads violating the updated oneOf validation rule will be rejected. | Update client-side schema definitions to respect the new oneOf constraint. |
Modified the strict schema constraint oneOf at */*/modifier in the response payload under status 500. | |||
| GET/payments/reconciliation/documents/v2/spaces/{spaceId}/documents/aggregations | Modified the strict schema constraint oneOf at */*/documentAggregations/aggregations/modifier in the response payload under status 200. | Payloads violating the updated oneOf validation rule will be rejected. | Update client-side schema definitions to respect the new oneOf constraint. |
Modified the strict schema constraint oneOf at */*/documentAggregations/aggregations/modifier in the response payload under status 400. | |||
| GET/payments/reconciliation/documents/v2/spaces/{spaceId}/documents/{documentId}/aggregations | Modified the strict schema constraint oneOf at */*/documentAggregations/aggregations/modifier in the response payload under status 200. | Payloads violating the updated oneOf validation rule will be rejected. | Update client-side schema definitions to respect the new oneOf constraint. |
Modified the strict schema constraint oneOf at */*/documentAggregations/aggregations/modifier in the response payload under status 400. |
InfoImprovements (Non-Breaking)
| Endpoint | Details | Impact |
|---|---|---|
| GET/payments/reconciliation/payments/v1/spaces/{spaceId}/payments/aggregations | Added the new optional response property under status 200 */*/paymentAggregations/paymentMethod. | Supply or consume */*/paymentAggregations/paymentMethod for enriched functionality. |
Added the new optional response property under status 400 */*/paymentAggregations/paymentMethod. | ||
| GET/payments/reconciliation/payments/v1/spaces/{spaceId}/payments/{paymentId}/aggregations | Added the new optional response property under status 200 */*/paymentAggregations/paymentMethod. | Supply or consume */*/paymentAggregations/paymentMethod for enriched functionality. |
Added the new optional response property under status 400 */*/paymentAggregations/paymentMethod. | ||
| GET/payments/reconciliation/payments/v2/spaces/{spaceId}/payments/aggregations | Added the new optional response property under status 200 */*/paymentAggregations/paymentMethod. | Supply or consume */*/paymentAggregations/paymentMethod for enriched functionality. |
Added the new optional response property under status 400 */*/paymentAggregations/paymentMethod. | ||
| GET/payments/reconciliation/payments/v2/spaces/{spaceId}/payments/{paymentId}/aggregations | Added the new optional response property under status 200 */*/paymentAggregations/paymentMethod. | Supply or consume */*/paymentAggregations/paymentMethod for enriched functionality. |
Added the new optional response property under status 400 */*/paymentAggregations/paymentMethod. |
Platform
Platform Event
DeprecatedDeprecated Endpoints
| Endpoint | Details | Impact |
|---|---|---|
| GET/platform/event/v1/entities/{entityId}/events | Marked as deprecated. | Will be removed in a future release. |
| POST/platform/event/v1/entities/{entityId}/events | ||
| GET/platform/event/v1/spaces/{spaceId}/events | ||
| POST/platform/event/v1/spaces/{spaceId}/events |
Platform Extension Management
InfoImprovements (Non-Breaking)
| Endpoint | Details | Impact |
|---|---|---|
| GET/platform/extension_mgmt/v1/applications | Added the new optional response property under status 200 applications/subscriptionOnly. | Supply or consume applications/subscriptionOnly for enriched functionality. |
| GET/platform/extension_mgmt/v1/applications/{applicationId} | Added the new optional response property under status 200 subscriptionOnly. | Supply or consume subscriptionOnly for enriched functionality. |
Updated the schema metadata example in the response payload under status 200. | Provides clearer guidance when using this property. |
Platform Partner
BreakingBreaking Changes
| Endpoint | Change | Impact | Migration |
|---|---|---|---|
| POST/workspace/partner/api/v1/spaces/{spaceId}/clients:batchAddTeamMember | Modified the strict schema constraint nullable at clientIds in the request payload. | Payloads violating the updated nullable validation rule will be rejected. | Update client-side schema definitions to respect the new nullable constraint. |
Modified the strict schema constraint nullable at clientIds in the request payload. | |||
Modified the strict schema constraint minItems at clientIds in the request payload. | Payloads violating the updated minItems validation rule will be rejected. | Update client-side schema definitions to respect the new minItems constraint. | |
| POST/workspace/partner/api/v1/spaces/{spaceId}/clients:batchAssignExtension | Modified the strict schema constraint minItems at clientIds in the request payload. | Payloads violating the updated minItems validation rule will be rejected. | Update client-side schema definitions to respect the new minItems constraint. |
| GET/workspace/partner/v1/spaces/{partnerSpaceId}/clients/{clientId}/files | Removed the query request property. | Client payloads including the query field will be rejected by the updated schema validation on this endpoint. | Remove the query parameter from request payloads and update client-side schema models. |
| GET/workspace/partner/v2/spaces/{partnerSpaceId}/clients/{clientId}/documents | |||
| GET/workspace/partner/v2/spaces/{partnerSpaceId}/clients/{clientId}/{folder}/content | |||
| GET/workspace/partner/v2/spaces/{partnerSpaceId}/clients/{clientId}/{folder}/directories/{directoryId}/content |
InfoImprovements (Non-Breaking)
| Endpoint | Details | Impact |
|---|---|---|
| DELETE/workspace/partner/api/v1/spaces/{spaceId}/clients/settings/template | Modified specification properties: securityRequirements. | No developer action required; specification-only change. |
| PATCH/workspace/partner/api/v1/spaces/{spaceId}/clients/settings/template | ||
| POST/workspace/partner/api/v1/spaces/{spaceId}/clients/settings:addTemplate | ||
| POST/workspace/partner/api/v1/spaces/{spaceId}/clients/settings:markTemplateAsDefault | ||
| POST/workspace/partner/api/v1/spaces/{spaceId}/clients:batchAddTeamMember | Added the new optional request property ql. | Supply or consume ql for enriched functionality. |
Updated the schema metadata description at clientIds in the request payload. | Provides clearer guidance when using this property. | |
Updated the schema metadata description at clientIds in the request payload. | ||
The clientIds property is no longer required in the request payload. | Clients can omit this property. | |
| POST/workspace/partner/api/v1/spaces/{spaceId}/clients:batchAssignExtension | Added the new optional request property ql. | Supply or consume ql for enriched functionality. |
The clientIds property is no longer required in the request payload. | Clients can omit this property. | |
| POST/workspace/partner/api/v1/spaces/{spaceId}/clients:bulkActivate | Modified specification properties: securityRequirements. | No developer action required; specification-only change. |
| GET/workspace/partner/v1/spaces/{partnerSpaceId}/clients/{clientId}/files | Added the new optional request property query. | Filter or enhance queries by utilizing the query parameter for more targeted results. |
| POST/workspace/partner/v1/spaces/{spaceId}/clients:importFromTemplate | Modified specification properties: securityRequirements. | No developer action required; specification-only change. |
| GET/workspace/partner/v2/spaces/{partnerSpaceId}/clients/{clientId}/documents | Added the new optional request property query. | Filter or enhance queries by utilizing the query parameter for more targeted results. |
Tax
Tax Configuration
InfoImprovements (Non-Breaking)
| Endpoint | Details | Impact |
|---|---|---|
| GET/tax/configuration/v1/spaces/{spaceId}/customPeppolTaxCategories | Updated the schema metadata description at results in the response payload under status 200. | Provides clearer guidance when using this property. |
| POST/tax/configuration/v1/spaces/{spaceId}/customPeppolTaxCategories | Updated the schema metadata description in the response payload under status 200. | Provides clearer guidance when using this property. |
| GET/tax/configuration/v1/spaces/{spaceId}/customPeppolTaxCategories/{categoryId} | ||
| PATCH/tax/configuration/v1/spaces/{spaceId}/customPeppolTaxCategories/{categoryId} | ||
| GET/tax/configuration/v1/spaces/{spaceId}/customPeppolTaxCategoryMappings | Added the new optional response property under status 200 results/peppolTaxCategory. | Supply or consume results/peppolTaxCategory for enriched functionality. |
Updated the schema metadata description at results/customPeppolTaxCategory in the response payload under status 200. | Provides clearer guidance when using this property. | |
Updated the schema metadata example in the response payload under status 200. | ||
| POST/tax/configuration/v1/spaces/{spaceId}/customPeppolTaxCategoryMappings | Added the new optional response property under status 200 peppolTaxCategory. | Supply or consume peppolTaxCategory for enriched functionality. |
Updated the schema metadata description at customPeppolTaxCategory in the response payload under status 200. | Provides clearer guidance when using this property. | |
Updated the schema metadata example in the response payload under status 200. | ||
| GET/tax/configuration/v1/spaces/{spaceId}/customPeppolTaxCategoryMappings/{mappingId} | Added the new optional response property under status 200 peppolTaxCategory. | Supply or consume peppolTaxCategory for enriched functionality. |
Updated the schema metadata description at customPeppolTaxCategory in the response payload under status 200. | Provides clearer guidance when using this property. | |
Updated the schema metadata example in the response payload under status 200. | ||
| PATCH/tax/configuration/v1/spaces/{spaceId}/customPeppolTaxCategoryMappings/{mappingId} | Added the new optional response property under status 200 peppolTaxCategory. | Supply or consume peppolTaxCategory for enriched functionality. |
Updated the schema metadata description at customPeppolTaxCategory in the response payload under status 200. | Provides clearer guidance when using this property. | |
Updated the schema metadata example in the response payload under status 200. | ||
| POST/tax/configuration/v1/spaces/{spaceId}/customPeppolTaxCategoryMappings/{mappingId}:clone | Added the new optional response property under status 200 peppolTaxCategory. | Supply or consume peppolTaxCategory for enriched functionality. |
Updated the schema metadata description at customPeppolTaxCategory in the response payload under status 200. | Provides clearer guidance when using this property. | |
Updated the schema metadata example in the response payload under status 200. | ||
| GET/tax/configuration/v1/spaces/{spaceId}/customVatexCodeMappings | Added the new optional response property under status 200 results/vatexCode. | Supply or consume results/vatexCode for enriched functionality. |
Updated the schema metadata description at results/customVatexCode in the response payload under status 200. | Provides clearer guidance when using this property. | |
Updated the schema metadata example in the response payload under status 200. | ||
| POST/tax/configuration/v1/spaces/{spaceId}/customVatexCodeMappings | Added the new optional response property under status 200 vatexCode. | Supply or consume vatexCode for enriched functionality. |
Updated the schema metadata description at customVatexCode in the response payload under status 200. | Provides clearer guidance when using this property. | |
Updated the schema metadata example in the response payload under status 200. | ||
| GET/tax/configuration/v1/spaces/{spaceId}/customVatexCodeMappings/{mappingId} | Added the new optional response property under status 200 vatexCode. | Supply or consume vatexCode for enriched functionality. |
Updated the schema metadata description at customVatexCode in the response payload under status 200. | Provides clearer guidance when using this property. | |
Updated the schema metadata example in the response payload under status 200. | ||
| PATCH/tax/configuration/v1/spaces/{spaceId}/customVatexCodeMappings/{mappingId} | Added the new optional response property under status 200 vatexCode. | Supply or consume vatexCode for enriched functionality. |
Updated the schema metadata description at customVatexCode in the response payload under status 200. | Provides clearer guidance when using this property. | |
Updated the schema metadata example in the response payload under status 200. | ||
| POST/tax/configuration/v1/spaces/{spaceId}/customVatexCodeMappings/{mappingId}:clone | Added the new optional response property under status 200 vatexCode. | Supply or consume vatexCode for enriched functionality. |
Updated the schema metadata description at customVatexCode in the response payload under status 200. | Provides clearer guidance when using this property. | |
Updated the schema metadata example in the response payload under status 200. | ||
| GET/tax/configuration/v1/spaces/{spaceId}/customVatexCodes | Updated the schema metadata description at results in the response payload under status 200. | Provides clearer guidance when using this property. |
| POST/tax/configuration/v1/spaces/{spaceId}/customVatexCodes | Updated the schema metadata description in the response payload under status 200. | Provides clearer guidance when using this property. |
| GET/tax/configuration/v1/spaces/{spaceId}/customVatexCodes/{codeId} | ||
| PATCH/tax/configuration/v1/spaces/{spaceId}/customVatexCodes/{codeId} | ||
| GET/tax/configuration/v1/spaces/{spaceId}/peppolTaxCategories/{categoryId} | ||
| GET/tax/configuration/v1/spaces/{spaceId}/peppolTaxCategoryMappings | Updated the schema metadata description at results/peppolTaxCategory in the response payload under status 200. | Provides clearer guidance when using this property. |
| GET/tax/configuration/v1/spaces/{spaceId}/peppolTaxCategoryMappings/{mappingId} | Updated the schema metadata description at peppolTaxCategory in the response payload under status 200. | Provides clearer guidance when using this property. |
Tax Countries
BreakingBreaking Changes
| Endpoint | Change | Impact | Migration |
|---|---|---|---|
| GET/tax/countries/v1/territories | Removed the query request property. | Client payloads including the query field will be rejected by the updated schema validation on this endpoint. | Remove the query parameter from request payloads and update client-side schema models. |
eInvoicing
eInvoicing Core
BreakingBreaking Changes
| Endpoint | Change | Impact | Migration |
|---|---|---|---|
| POST/documents/core/v1/spaces/documents:validate | API path removed without deprecation. | Invocations targeting this endpoint will fail immediately with an HTTP 404 Not Found routing error. | Re-route client integrations to current supported paths. |
| GET/documents/core/transaction/v1/spaces/{spaceId}/documents | Removed the query request property. | Client payloads including the query field will be rejected by the updated schema validation on this endpoint. | Remove the query parameter from request payloads and update client-side schema models. |
| GET/documents/core/transaction/v1/spaces/{spaceId}/documents:count | |||
| GET/documents/core/transaction/v1/spaces/{spaceId}/files | |||
| GET/documents/core/transaction/v1/spaces/{spaceId}/{folder}/documents:count | |||
| GET/documents/core/transaction/v2/spaces/{spaceId}/documents | |||
| GET/documents/core/transaction/v2/spaces/{spaceId}/{folder}/content | |||
| GET/documents/core/transaction/v2/spaces/{spaceId}/{folder}/directories/{directoryId}/content | |||
| POST/documents/core/v1/spaces/{spaceId}/documents/{documentId}:validate | Modified the strict schema constraint content in the response payload under status 202. | Payloads violating the updated content validation rule will be rejected. | Update client-side schema definitions to respect the new content constraint. |
NewNew Endpoints
| Endpoint | Description |
|---|---|
| PATCH/documents/core/transaction/v1/spaces/{spaceId}/documents/{documentId}/representations/{documentRepresentationId}:jsonpatch | Adds a new operation for this resource. |
InfoImprovements (Non-Breaking)
| Endpoint | Details | Impact |
|---|---|---|
| GET/documents/core/transaction/v1/spaces/{spaceId}/files | Added the new optional request property query. | Filter or enhance queries by utilizing the query parameter for more targeted results. |
| GET/documents/core/transaction/v2/spaces/{spaceId}/documents |
DeprecatedDeprecated Endpoints
| Endpoint | Details | Impact |
|---|---|---|
| PATCH/documents/core/transaction/v1/spaces/{spaceId}/{folder}/documents/{documentId} | Marked as deprecated. | Will be removed in a future release. |
eInvoicing Customers & Suppliers
BreakingBreaking Changes
| Endpoint | Change | Impact | Migration |
|---|---|---|---|
| GET/network/core/transaction/v2/spaces/{spaceId}/connections | Removed the query request property. | Client payloads including the query field will be rejected by the updated schema validation on this endpoint. | Remove the query parameter from request payloads and update client-side schema models. |
| GET/network/core/transaction/v3/spaces/{spaceId}/connections |
InfoImprovements (Non-Breaking)
| Endpoint | Details | Impact |
|---|---|---|
| GET/network/core/transaction/v2/spaces/{spaceId}/connections | Added the new optional request property query. | Filter or enhance queries by utilizing the query parameter for more targeted results. |
| GET/network/core/transaction/v3/spaces/{spaceId}/connections |
DeprecatedDeprecated Endpoints
eInvoicing Payment
BreakingBreaking Changes
| Endpoint | Change | Impact | Migration |
|---|---|---|---|
| POST/documents/payment/business/v1/spaces/{spaceId}/payments/documents:validate | Added the new FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD type. | Update models to accept and handle the FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD type. |
Added the new RESTRICTED_ZONE enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_ZONE type. | Update models to accept and handle the RESTRICTED_ZONE type. | |
Added the new RESTRICTED_ZONE_CURRENCY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_ZONE_CURRENCY type. | Update models to accept and handle the RESTRICTED_ZONE_CURRENCY type. | |
Added the new RESTRICTED_CURRENCY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_CURRENCY type. | Update models to accept and handle the RESTRICTED_CURRENCY type. | |
Added the new UNSUPPORTED_CURRENCY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the UNSUPPORTED_CURRENCY type. | Update models to accept and handle the UNSUPPORTED_CURRENCY type. | |
Added the new COLLECTION_SCHEDULED_TOO_EARLY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the COLLECTION_SCHEDULED_TOO_EARLY type. | Update models to accept and handle the COLLECTION_SCHEDULED_TOO_EARLY type. | |
Added the new CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH type. | Update models to accept and handle the CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH type. | |
Added the new INACTIVE_COLLECTION_CONSENT enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the INACTIVE_COLLECTION_CONSENT type. | Update models to accept and handle the INACTIVE_COLLECTION_CONSENT type. | |
| POST/documents/payment/business/v2/spaces/{spaceId}/payments/documents:validate | Added the new FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD type. | Update models to accept and handle the FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD type. |
Added the new RESTRICTED_ZONE enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_ZONE type. | Update models to accept and handle the RESTRICTED_ZONE type. | |
Added the new RESTRICTED_ZONE_CURRENCY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_ZONE_CURRENCY type. | Update models to accept and handle the RESTRICTED_ZONE_CURRENCY type. | |
Added the new RESTRICTED_CURRENCY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_CURRENCY type. | Update models to accept and handle the RESTRICTED_CURRENCY type. | |
Added the new UNSUPPORTED_CURRENCY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the UNSUPPORTED_CURRENCY type. | Update models to accept and handle the UNSUPPORTED_CURRENCY type. | |
Added the new COLLECTION_SCHEDULED_TOO_EARLY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the COLLECTION_SCHEDULED_TOO_EARLY type. | Update models to accept and handle the COLLECTION_SCHEDULED_TOO_EARLY type. | |
Added the new CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH type. | Update models to accept and handle the CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH type. | |
Added the new INACTIVE_COLLECTION_CONSENT enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the INACTIVE_COLLECTION_CONSENT type. | Update models to accept and handle the INACTIVE_COLLECTION_CONSENT type. | |
Added the new UNSUPPORTED_CURRENCY_EXCHANGE enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the UNSUPPORTED_CURRENCY_EXCHANGE type. | Update models to accept and handle the UNSUPPORTED_CURRENCY_EXCHANGE type. | |
Added the new FEE_NOT_ACCEPTED_BY_PSU enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the FEE_NOT_ACCEPTED_BY_PSU type. | Update models to accept and handle the FEE_NOT_ACCEPTED_BY_PSU type. | |
Added the new LARGE_AMOUNT_REQUIRES_SYS_APPROVAL enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the LARGE_AMOUNT_REQUIRES_SYS_APPROVAL type. | Update models to accept and handle the LARGE_AMOUNT_REQUIRES_SYS_APPROVAL type. | |
Added the new TRANSACTION_LIMIT_EXCEEDED enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the TRANSACTION_LIMIT_EXCEEDED type. | Update models to accept and handle the TRANSACTION_LIMIT_EXCEEDED type. | |
Added the new UNVERIFIABLE_EXTERNAL_COLLECT_CONSENT enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the UNVERIFIABLE_EXTERNAL_COLLECT_CONSENT type. | Update models to accept and handle the UNVERIFIABLE_EXTERNAL_COLLECT_CONSENT type. | |
Added the new DISABLED_COLLECTION_METHOD enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the DISABLED_COLLECTION_METHOD type. | Update models to accept and handle the DISABLED_COLLECTION_METHOD type. | |
Added the new FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD type. | Update models to accept and handle the FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD type. | |
Added the new RESTRICTED_ZONE enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_ZONE type. | Update models to accept and handle the RESTRICTED_ZONE type. | |
Added the new RESTRICTED_ZONE_CURRENCY enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_ZONE_CURRENCY type. | Update models to accept and handle the RESTRICTED_ZONE_CURRENCY type. | |
Added the new RESTRICTED_CURRENCY enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_CURRENCY type. | Update models to accept and handle the RESTRICTED_CURRENCY type. | |
Added the new UNSUPPORTED_CURRENCY enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the UNSUPPORTED_CURRENCY type. | Update models to accept and handle the UNSUPPORTED_CURRENCY type. | |
Added the new COLLECTION_SCHEDULED_TOO_EARLY enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the COLLECTION_SCHEDULED_TOO_EARLY type. | Update models to accept and handle the COLLECTION_SCHEDULED_TOO_EARLY type. | |
Added the new CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH type. | Update models to accept and handle the CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH type. | |
Added the new INACTIVE_COLLECTION_CONSENT enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the INACTIVE_COLLECTION_CONSENT type. | Update models to accept and handle the INACTIVE_COLLECTION_CONSENT type. | |
| POST/documents/payment/business/v3/spaces/{spaceId}/payments/documents:validate | Added the new FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD type. | Update models to accept and handle the FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD type. |
Added the new RESTRICTED_ZONE enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_ZONE type. | Update models to accept and handle the RESTRICTED_ZONE type. | |
Added the new RESTRICTED_ZONE_CURRENCY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_ZONE_CURRENCY type. | Update models to accept and handle the RESTRICTED_ZONE_CURRENCY type. | |
Added the new RESTRICTED_CURRENCY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_CURRENCY type. | Update models to accept and handle the RESTRICTED_CURRENCY type. | |
Added the new UNSUPPORTED_CURRENCY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the UNSUPPORTED_CURRENCY type. | Update models to accept and handle the UNSUPPORTED_CURRENCY type. | |
Added the new COLLECTION_SCHEDULED_TOO_EARLY enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the COLLECTION_SCHEDULED_TOO_EARLY type. | Update models to accept and handle the COLLECTION_SCHEDULED_TOO_EARLY type. | |
Added the new CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH type. | Update models to accept and handle the CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH type. | |
Added the new INACTIVE_COLLECTION_CONSENT enum value to the validationResult/documentsMessages/messages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the INACTIVE_COLLECTION_CONSENT type. | Update models to accept and handle the INACTIVE_COLLECTION_CONSENT type. | |
Added the new UNSUPPORTED_CURRENCY_EXCHANGE enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the UNSUPPORTED_CURRENCY_EXCHANGE type. | Update models to accept and handle the UNSUPPORTED_CURRENCY_EXCHANGE type. | |
Added the new FEE_NOT_ACCEPTED_BY_PSU enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the FEE_NOT_ACCEPTED_BY_PSU type. | Update models to accept and handle the FEE_NOT_ACCEPTED_BY_PSU type. | |
Added the new LARGE_AMOUNT_REQUIRES_SYS_APPROVAL enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the LARGE_AMOUNT_REQUIRES_SYS_APPROVAL type. | Update models to accept and handle the LARGE_AMOUNT_REQUIRES_SYS_APPROVAL type. | |
Added the new TRANSACTION_LIMIT_EXCEEDED enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the TRANSACTION_LIMIT_EXCEEDED type. | Update models to accept and handle the TRANSACTION_LIMIT_EXCEEDED type. | |
Added the new UNVERIFIABLE_EXTERNAL_COLLECT_CONSENT enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the UNVERIFIABLE_EXTERNAL_COLLECT_CONSENT type. | Update models to accept and handle the UNVERIFIABLE_EXTERNAL_COLLECT_CONSENT type. | |
Added the new DISABLED_COLLECTION_METHOD enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the DISABLED_COLLECTION_METHOD type. | Update models to accept and handle the DISABLED_COLLECTION_METHOD type. | |
Added the new FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD type. | Update models to accept and handle the FIELD_REQUIREMENTS_FOR_EXECUTION_METHOD type. | |
Added the new RESTRICTED_ZONE enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_ZONE type. | Update models to accept and handle the RESTRICTED_ZONE type. | |
Added the new RESTRICTED_ZONE_CURRENCY enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_ZONE_CURRENCY type. | Update models to accept and handle the RESTRICTED_ZONE_CURRENCY type. | |
Added the new RESTRICTED_CURRENCY enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the RESTRICTED_CURRENCY type. | Update models to accept and handle the RESTRICTED_CURRENCY type. | |
Added the new UNSUPPORTED_CURRENCY enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the UNSUPPORTED_CURRENCY type. | Update models to accept and handle the UNSUPPORTED_CURRENCY type. | |
Added the new COLLECTION_SCHEDULED_TOO_EARLY enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the COLLECTION_SCHEDULED_TOO_EARLY type. | Update models to accept and handle the COLLECTION_SCHEDULED_TOO_EARLY type. | |
Added the new CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH type. | Update models to accept and handle the CREDITOR_ACCOUNT_VS_COUNTERPARTY_AMOUNT_MISMATCH type. | |
Added the new INACTIVE_COLLECTION_CONSENT enum value to the validationResult/paymentMessages/code response property under status 200. | Strict parsers will fail to deserialize when returning records with the INACTIVE_COLLECTION_CONSENT type. | Update models to accept and handle the INACTIVE_COLLECTION_CONSENT type. | |
| GET/documents/payment/pay/v1/spaces/{spaceId}/documents/{documentId}/balanceOffsets | Added the new IN_TRANSIT enum value to the balanceOffsets/payment/levelOfCertainty response property under status 200. | Strict parsers will fail to deserialize when returning records with the IN_TRANSIT type. | Update models to accept and handle the IN_TRANSIT type. |
| POST/documents/payment/pay/v1/spaces/{spaceId}/documents:balanceOffsets |
NewNew Endpoints
| Endpoint | Description |
|---|---|
| POST/documents/payment/business/v4/spaces/{spaceId}/payments/documents:execute | Adds a new operation for this resource. |
| POST/documents/payment/business/v4/spaces/{spaceId}/payments/documents:validate |
InfoImprovements (Non-Breaking)
| Endpoint | Details | Impact |
|---|---|---|
| POST/documents/payment/business/v1/spaces/{spaceId}/payments/documents:execute | Modified specification properties: operationID. | No developer action required; specification-only change. |
| POST/documents/payment/business/v2/spaces/{spaceId}/payments/documents:execute |
DeprecatedDeprecated Endpoints
| Endpoint | Details | Impact |
|---|---|---|
| POST/documents/payment/business/v3/spaces/{spaceId}/payments/documents:execute | Marked as deprecated. | Will be removed in a future release. |
| POST/documents/payment/business/v3/spaces/{spaceId}/payments/documents:validate | ||
| POST/documents/payment/transaction/v1/spaces/{spaceId}/documents:paydetails |
eInvoicing Document Connectors
BreakingBreaking Changes
| Endpoint | Change | Impact | Migration |
|---|---|---|---|
| POST/network/documents/spaces/connectors/afnor/v1/directory-line/search | Removed the request property sorting/items/sortingOrder. | Client payloads including the sorting/items/sortingOrder field will be rejected. | Remove the sorting/items/sortingOrder parameter from request payloads and update client-side schema models. |
Removed the optional response property search/sorting/items/sortingOrder under status 200. | Clients relying on the search/sorting/items/sortingOrder response property will no longer receive it. | Remove the search/sorting/items/sortingOrder parameter from response payload under status 200 models. | |
| POST/network/documents/spaces/connectors/afnor/v1/routing-code/search | Added the new startWith enum value to the search/filters/addressLines/op response property for status 200. | Strict parsers will fail to deserialize when returning records with the startWith value. | Update models to accept and handle the startWith value. |
Added the new startWith enum value to the search/filters/locality/op response property for status 200. | |||
| POST/network/documents/spaces/connectors/afnor/v1/siren/search | Removed the request property sorting/items/sortingOrder. | Client payloads including the sorting/items/sortingOrder field will be rejected. | Remove the sorting/items/sortingOrder parameter from request payloads and update client-side schema models. |
Removed the optional response property search/sorting/items/sortingOrder under status 200. | Clients relying on the search/sorting/items/sortingOrder response property will no longer receive it. | Remove the search/sorting/items/sortingOrder parameter from response payload under status 200 models. | |
Added the new startWith enum value to the search/filters/businessName/op response property for status 200. | Strict parsers will fail to deserialize when returning records with the startWith value. | Update models to accept and handle the startWith value. | |
| POST/network/documents/spaces/connectors/afnor/v1/siret/search | Removed the request property sorting/items/sortingOrder. | Client payloads including the sorting/items/sortingOrder field will be rejected. | Remove the sorting/items/sortingOrder parameter from request payloads and update client-side schema models. |
Removed the optional response property search/sorting/items/sortingOrder under status 200. | Clients relying on the search/sorting/items/sortingOrder response property will no longer receive it. | Remove the search/sorting/items/sortingOrder parameter from response payload under status 200 models. | |
Added the new startWith enum value to the search/filters/addressLines/op response property for status 200. | Strict parsers will fail to deserialize when returning records with the startWith value. | Update models to accept and handle the startWith value. | |
Added the new startWith enum value to the search/filters/locality/op response property for status 200. | |||
Added the new startWith enum value to the search/filters/name/op response property for status 200. |
InfoImprovements (Non-Breaking)
| Endpoint | Details | Impact |
|---|---|---|
| POST/network/documents/spaces/connectors/afnor/v1/directory-line/search | Added the new optional request property sorting/items/order. | Supply or consume sorting/items/order for enriched functionality. |
Added the optional response property search/sorting/items/order under status 200. | ||
| POST/network/documents/spaces/connectors/afnor/v1/routing-code/search | Added the new startWith enum value to the request property filters/addressLines/op. | You can now use this new enum value in requests. |
Added the new startWith enum value to the request property filters/locality/op. | ||
| POST/network/documents/spaces/connectors/afnor/v1/siren/search | Added the new optional request property sorting/items/order. | Supply or consume sorting/items/order for enriched functionality. |
Added the new startWith enum value to the request property filters/businessName/op. | You can now use this new enum value in requests. | |
Added the optional response property search/sorting/items/order under status 200. | Supply or consume search/sorting/items/order for enriched functionality. | |
| POST/network/documents/spaces/connectors/afnor/v1/siret/search | Added the new optional request property sorting/items/order. | Supply or consume sorting/items/order for enriched functionality. |
Added the new startWith enum value to the request property filters/addressLines/op. | You can now use this new enum value in requests. | |
Added the new startWith enum value to the request property filters/locality/op. | ||
Added the new startWith enum value to the request property filters/name/op. | ||
Added the optional response property search/sorting/items/order under status 200. | Supply or consume search/sorting/items/order for enriched functionality. |