Alternate Synced Account Object
S
Shawn
Right now the only "Synced" account is the default Plaid managed accounts. To support future third-party tools, create an object that is as close to the Plaid object while being manually managed by said third party. This should show similarly as the Plaid accounts and have the option to say what third party added it and other similar labels elsewhere.
Log In
J
JP Shipherd
Shawn can you elaborate on your use case? Currently 3rd party apps create manual accounts for these types of transactions. Currently these accounts are manageable by the user in the Setup/Accounts page and by the API using the /assets endpoint.
Is there a use case that the current model doesn't support?
D
Dylan Mazurek
JP Shipherd for my use cases I would suggest allowing the syncing metadata to be store by 3rd party apps, things like "external id" to link a synced account with a external account id. Also metadata like "last synced" and fails would be cool to have logged.
J
JP Shipherd
Dylan Mazurek can you describe the use case in non technical terms? I'm not completely following what you are suggesting. I understand that you would like an additional account type beyond assets and plaid accounts for 3rd party transaction imports to use, but I'm not sure why.
One thing that we are currently considering is to add not only an external_id to the asset object but also "custom_metdata" which would allow a developer to store their own JSON with the account. There is also another feature request to set a flag on assets to make them "only updateable by API". Perhaps these things would meet the use case?