The first endpoints of our current API (v1) are almost 10 years old. They’ve been serving hundreds of developers and many customers over the years, but they could be more intuitive, coherent, and far more pleasant to use. That’s why we’re building an entirely new API (v2) from the ground up, so that our current API (v1) can finally get the retirement it deserves.





To improve authentication security we’ve decided to move from our current authentication mechanism to OAuth 2.0.





We’re going to serve our API endpoints from its own subdomain (

) to have more infrastructural flexibility, enabling better traffic isolation and infrastructure scaling.





In V1 we have a mix of application/x-www-form-urlencoded, JSON, and sometimes even form-urlencoded fields containing a JSON string as a value. In v2 we’re committing to JSON as the standard data format, following general REST principles with some RPC-style action endpoints where appropriate.





We’ll use carefully picked HTTP status codes along with internal error codes and messages when HTTP status codes alone aren’t sufficient.





We're also committing to maintaining a full, up-to-date OpenAPI specification with well-thought-out examples. 

General upcoming improvements

The new Accounting API will also support 

Accounting API

With the upcoming Customers API you'll be able to 

 customers with a cleaner URL structure and a more consistent request and response format. 

We're also planning to implement highly requested features, such as the 

Customers API

GET responses will include a new flag indicating whether a 

We're also adding cross-endpoint validation to 

Dimensions API

API v2 will introduce a dedicated Payroll API for managing payroll entries. 

Payroll API

Products used to be manageable only through the Sales Invoices API. We're now adding 

Products API

The Purchases API is finally getting the highly requested capability 

And to make your life even easier, we're enhancing the 

, so you can get everything you need with fewer API calls.

Purchases API

With the introduction of the dedicated Products and Customers APIs, 

, as that responsibility now belongs to their own dedicated endpoints.

Sales invoices API

We’re building a new API from the ground up. This is your chance to influence what it looks and feels like.

Help us create the upcoming Fennoa API v2