API Version Upgrade Guide
Loading...
Loading...
Loading...
Quiltt uses date-based API versioning. Breaking changes are only introduced in new versions, so your existing integration continues working until you explicitly upgrade. You can check your current version in the Quiltt Dashboard under each API key's settings.
| Version | Released | What Changed |
|---|---|---|
2026-04-01 | April 1, 2026 | Removes deprecated fields; updates Ntropy enrichment to V3 |
2025-04-01 | April 1, 2025 | Renames Product and Feature enum values |
2024-01-01 | January 1, 2024 | Oldest supported version |
If you're upgrading across multiple versions (e.g. from 2024-01-01 to 2026-04-01), review the changes for each version in between.
Quiltt-Version header to try the new version without changing your key:Test with the Quiltt-Version header in your development environment before updating the version on your API key. The header override applies only to that single request.
This version removes previously deprecated fields and arguments, and updates the Ntropy enrichment data model to V3.
If your queries reference any of these fields, update them before upgrading.
| Type | Removed Field | Use Instead |
|---|---|---|
Account | type | kind or taxonomy |
Account | origin | provider |
Connection | features | products |
Holding | account | Query from Account.holdings |
Holding | remoteData | Query from Account.remoteData |
Image | _sourcename | Remove from query |
Merchant | metadata | Remove from query |
Merchant | state | Remove from query |
ConnectionDisconnectPayload | errors | Handle via GraphQL errors |
| Type | Field | Removed Argument | Use Instead |
|---|---|---|---|
Connection | accounts | search | filter |
Account / Connection | transactions | search | filter |
AccountFilter | — | type | kind |
| Enum | Removed Value |
|---|---|
TransactionStatus | PROJECTED |
| Removed | Use Instead |
|---|---|
connectionUpdated | connectionSynced |
location type changeThe location field on RemoteDataNtropyEnrichedTransaction changed from a plain String to a structured RemoteDataNtropyLocation object. If you only need the original string, use location.rawAddress. The new location.structured sub-object provides parsed address components:
Before (≤ 2025-04-01):
After (2026-04-01):
The following fields on RemoteDataNtropyEnrichedTransaction are removed. Use the V3 equivalents:
| Removed Field | V3 Replacement |
|---|---|
merchant | entities.counterparty.name |
merchantId | entities.counterparty.id |
person | entities.counterparty.type |
logo | entities.counterparty.logo |
website | entities.counterparty.website |
mcc | entities.counterparty.mccs |
labels | categories |
transactionType | categories |
locationStructured | location.structured |
transactionId | id |
recurrence | — |
recurrenceGroup | — |
recurrenceGroupId | — |
The Ntropy enrichment data in the REST API is returned under documents["api.ntropy.com"], keyed by endpoint path. In this version, the V2 path (/v2/transactions/{mode}) is removed for integrations enabled after April 1, 2026. Older integrations continue to receive both paths.
The document path and body structure differ between versions:
V2 path (/v2/transactions/{mode}):
V3 path (/v3/transactions):
If your code accesses Ntropy data via the REST API, update it to read from the /v3/transactions path and use the nested body structure.
This version replaces the features field with products on Connections, using more descriptive enum values:
| Removed | Replacement |
|---|---|
BALANCES | ACCOUNT_BALANCE_REFRESHES |
STATEMENTS | ACCOUNT_STATEMENTS |
TRANSACTIONS | ACCOUNT_BALANCES_AND_TRANSACTIONS |
If your queries use features, switch to products with the new values:
This is the oldest currently supported API version. If you're still on 2024-01-01, review the changes in each version above to plan your upgrade.