Skip to main content
This guide is for partners who used the Expenses API to build custom expense-related workflows — for example syncing expenses to project management software, building dashboards, or generating reports. If you were building an accounting export integration, see Migrate to the Export API instead.

​
New to the Accounting Entries API?

API Overview

What an Accounting Entry is and how the API is structured.

API Scopes

Required scope: accounting-entries:read.

Generate API Keys

How to generate standalone API keys for authenticating your integration.

Standalone API Key Guide

End-to-end guide for authenticating with standalone API keys.

Standalone API Keys with Postman

How to make API calls using standalone API keys in Postman.

​
Getting Started

You’ll need API credentials with at least the accounting-entries:read scope. Once authenticated, the two main endpoints you’ll use are:

​
Key Differences

  • Field names and structure have changed. See Field Mapping below.
  • The Accounting Entries API uses cursor-based pagination.

​
Field Mapping

The table below maps fields from the Expense model to their equivalents in the AccountingEntry model.
  • — : field is not available in the AccountingEntry model
  • * : data is the same but represented differently. See the Accounting Entries API reference for details.

​
New Fields in AccountingEntryV1

The following fields are available in AccountingEntryV1 with no equivalent in the Expense API.

​
Other Use Cases

For use cases beyond what’s described in this guide, please fill in this form to let us know.