Loading...
Search the Quiltt documentation
Loading...
April 2026
RemoteDataFingoalEnrichedTransaction matching FinGoal API v3.1.3: accountType, address, city, settlement, state, subtype, transactionTagsId, website, and zipCodeRemoteDataFingoalEnrichedTransaction fields as nullable to accurately reflect FinGoal API v3.1.3 responsesTransaction.date field description to explain that for POSTED transactions it reflects the settlement date, and for PENDING transactions it reflects when the transaction was initiatedmetadata field on API Key REST schemaGET /v1/accounts/:accountId/ach_numbers response codes — return 202 Accepted while Finicity ACH numbers are fetched asynchronously, 410 Gone for permanently unverifiable accounts, and distinct 403 responses for not-verified and closed statesINVALID_INPUT errors when launching Plaid Link with unprovisioned products/v1/connections/{connectionId}/transactions/refresh endpoint (now in closed beta)RemoteDataNtropyEnrichedTransaction.location field appearing as locationV3 in schema introspection and not resolving as an object for 2026-04-01+ API versionrecurrence, recurrence_group_id, recurrence_group) returning null for accounts enriched with Ntropy V3Connection.products so ACCOUNT_TRANSACTIONS_REFRESHES resolves without errormask value when the provider returns an account name instead of a number in the display fieldaccount_transactions_refreshes support for any institution with transactions; now correctly requires Plaid's transactions_refresh product