Chase just ships broken APIs. I work with Chase APIs every day through Plaid and Akoya. There are a whole list of ongoing known issues, from duplicates, to missing transactions. JPMorgan doesn’t know how to or doesn’t want to ship a proper API.
It is not difficult at all to serve 2 billion requests a month for transaction data. A single server could handle that.
Why go public with this? If anything, this is a contractual issue between JPMorgan and the API user. API usage terms should have been spelled out in contracts.
Because there is value in ensuring the public knows their use of Plaid is adversely effecting the banking system. Plaid in it's original incarnation was a straight up ToS violation for most financial firms, as they used privileged credentials to scrape the User's transaction history far in excess of what would be expected or reasonable.
Chase just ships broken APIs. I work with Chase APIs every day through Plaid and Akoya. There are a whole list of ongoing known issues, from duplicates, to missing transactions. JPMorgan doesn’t know how to or doesn’t want to ship a proper API.
It is not difficult at all to serve 2 billion requests a month for transaction data. A single server could handle that.
This is obviously a PR play to cut out middlemen. Related accusation: https://www.thestreet.com/crypto/policy/exclusive-jpmorgan-h...
Why go public with this? If anything, this is a contractual issue between JPMorgan and the API user. API usage terms should have been spelled out in contracts.
Because there is value in ensuring the public knows their use of Plaid is adversely effecting the banking system. Plaid in it's original incarnation was a straight up ToS violation for most financial firms, as they used privileged credentials to scrape the User's transaction history far in excess of what would be expected or reasonable.
Maybe they should design an API that doesn't require constant polling for updates? Pubsub isn't exactly new technology.