Loading...
Loading...
May 2025
SFOX as a supported processor token typeerror_code_reason field in error handling{ required: true } instead of 'required')style_settings on ConnectorclientName field from ConnectorPlaidInitializeInput — Plaid application name is now controlled by QuilttPlaidTransaction.category and PlaidTransaction.categoryId fields from Remote DataAccountMerchantFilter input type, standalone merchant and merchants queries, and merchantUpdate mutation from the schemaMerchant type on Transaction to be sourced directly from API documents rather than the Account::Merchant modelPaveTransaction type with additional fields from Pave's transaction enrichment APIAccountOwner on Plaid and MX Connection typesAccountOwner.remoteData field description capitalisation ("Remote Data")POST /v1/introspect/api_key, POST /v1/introspect/session_token, and POST /v1/introspect/processor_token endpoints to the Auth APIGET /v1/client in favour of POST /v1/introspect/api_keyGET /v1/users/session in favour of POST /v1/introspect/session_tokenv1/accounts/:id/ach endpointaccountId field on ProcessorToken with a nested account object containing id and typeenvironment object to ProcessorToken schema, exposing id and modeexternallyManaged optional on the Plaid import endpointexternallyManaged to true for all ProcessorToken importsAccount.holdings remoteData field by exposing AccountHoldingType instead of the legacy HoldingTypeprofile_id field from Sync Enrichment endpoint documentationenvironment property to ProcessorToken schemaissuer field on processor token endpoints to accept input (remove erroneous readOnly constraint)403 Integration not enabled responseaccount.verified events not firing for Finicity accounts