On Wednesday we released some pretty exciting updates to our API and wanted to make sure you were aware of them.

Ever since its debut, the API has used a more restrictive set of permissions than the application. This made things a little simpler for us, but it didn't help our users or third-party add-on developers. It meant that certain third-party applications simply weren't as useful for customers who had multiple staff members sharing a single FreshBooks account. We've received many requests from developers to open up permissions in the API so that they more closely follow the permission settings in the application. You have been heard!

On January 4, 2010, we will be disabling SSLv2 and ciphers with keys smaller than 128 bits.

FreshBooks now supports OAuth for secure API authorization.