The end of Mint.com (and Mojito) is coming soon...

 Hi All,

I'm sure you have all heard by now that Intuit is shutting down Mint on January 1, 2024, and encouraging users to switch to Credit Karma (which is also owned by Intuit). Since Credit Karma almost certainly has different APIs (application programming interfaces) than Mint, this switch will effectively kill Mojito also. We had a good 10 year run with Mojito, but our luck has finally run out.

Personally, I haven't yet figured out what I'm going to do next to download and aggregate my financial data. I'm kind of hesitant to switch to Credit Karma because I'm fairly certain Intuit's business model will be to sell everything about me to their "partners" (just like they do with Mint) ... because free isn't really "free", right?

Under the hood, Credit Karma uses Plaid, which is a financial programming platform that provides APIs for accessing thousands of financial institutions. My initial thought was to use Plaid directly and copy, or customize, one of the existing solutions on GitHub to fetch my financial data: https://github.com/search?q=plaid+google+sheets&type=repositories. Unfortunately,  I discovered that I can't connect to my bank, credit card, or investment company using Plaid's Quickstart application, so that plan might not work out (or, at least, will take more time to sort out than I expected). However, you might have better luck. I highly recommend you check out that link. Maybe you'll find a solution that works for you!

IF I am able to come up with a solution that would be useful to others, I'll post a message here. Good luck to all of you. Thanks for being devoted Mojito users all these years!

-b3

Mojito is broken due to Mint UI overhaul

Hi All,

tl;dr
If you are wondering why Mojito no longer works, it's because of the new Mint user interface.

Details:
Around the beginning of 2022, Mint started automatically switching users over to a new user interface (UI). The new UI has a completely different programming interface (API) which effectively breaks Mojito. So any users that have the new Mint UI can no longer use Mojito to fetch and update their Mint data. My account was finally converted to the new UI a few weeks ago (I think I was one of the last?), so Mojito is broken for me, too.

My goal is to update Mojito so it will work with the new Mint UI, but I can't say with any confidence when that will be. My life and responsibilities are very different than they were when I originally created Mojito in 2013. Things are super busy for me right now. I'm sure many of you can relate to that overwhelming feeling where choosing to work on one thing means that something else is not getting done. That's my situation right now. Unfortunately, Mojito is not one of the projects where you can spend 15 minutes on it here and there. It requires several hours at a time, which is usually only possible late at night. And, I don't know about you, but I am already feeling pretty tired lately.

Again, I really do want to get Mojito working again, both for myself and for the handful of dedicated users out there. I just don't want to give you any false expectations about when that will happen.

Cheers,
-b3

Latest version of Chrome requires extra step to get Mint authentication info

Hi All,

It appears that Chrome moved the "Form Data" section to a separate tab within the DevTools / Network window. You now have to copy the data from the "Headers" tab (to get the cookies) and the "Payload" tab (to get the token).

Mojito Version 1.2.1 is available - fixes "UiApp has been deprecated" error

Hi All,

Around the end of January 2019, Mojito started displaying the following error when you tried to import transactions, import account data, or reconcile an account:

"UiApp has been deprecated. Please use HtmlService instead."

The reason for this error was that Google had ended support for the UiApp component, which Mojito was using to display several dialog windows. 

I have fixed this issue. Mojito now uses HtmlService (as the error message recommends). The new version is 1.2.1. As always, you can download a new copy, or you can upgrade your existing copy following the easy steps on the FAQ page.

-b3

Mojito 1.2.0 is now Available

Hi All,

Version 1.2.0 of Mojito is now available from the Download page. Changes in this version:

• A few UI improvements, like new buttons at the top of the TxnData, AccountData, and Reconcile sheets.
• Fixes to a few bugs.
• All of the source code for MojitoLib (the code that makes Mojito work) is now available on GitHub:  https://github.com/b3devs/MojitoLib
• For those who would like to modify the code to their liking, the development process is now easier (though still not "easy" exactly). Sparse instructions are provided on the GitHub page.

Because of the UI changes, you must download a new copy of Mojito to get this new version.

Cheers,

- b3

The Mojito Chrome plugin is not mine

Many of you probably already know this, but it has just come to my attention that there is a Chrome plugin called "Mojito" out there. It even has the same tag line: "mint with a kick"!? Go figure.

I haven't used this plugin, but from what I can tell it appears to be a "mint assistant" of sorts that modifies the mint.com web pages and adds new features.

The reason for this post is just to let you know that the Mojito Chrome plugin is in no way associated with the Mojito Google spreadsheet that I have created here. I do not know the developer of the plugin and have never communicated with him / her, so I cannot vouch for it in any way. Don't let that stop you from using it, though. :)

Cheers,
-b3

Mint change - get the authentication headers from "track.xevent" instead of "oauth2"

Hi All,

Just a quick post. Mint changed something and you can no longer get the required authentication headers by using the "oath2" request. You must now search for and copy all of the headers from the track.xevent request. (Also, fyi, I only see the track.xevent header when I view the "Overview" page on mint.com.)

I have updated the Mint Authentication Steps page with this new information (but I still need to updated the screenshot).

-b3