dotConnect for FreshBooks
Version
3.3.248
License
Shareware
Trial Limitations
Fully functional 30-day trial, no credit card. Needs a free Devart account
Operating Systems
Windows, Linux, macOS (x64 and x86). Installer and Visual Studio integration on Windows, NuGet package on all platforms
System Requirements
.NET 5 to 11, .NET Core 2.0 to 3.1, .NET Standard 2.0/2.1 or .NET Framework 4.5 to 4.8. Visual Studio 2015 to 2026 for design-time tools. FreshBooks account and app credentials
File Size
16.72 MB
Release Date
11/11/2026
Last Updated
11/14/2026
523 views 0 downloads
ADO.NET provider for FreshBooks invoices, clients and reports via SQL in .NET

dotConnect for FreshBooks: FreshBooks Invoices, Expenses and Reports as SQL Tables in .NET

dotConnect for FreshBooks is Devart's $339.95 ADO.NET data provider for .NET developers who need to pull FreshBooks accounting data (clients, invoices, estimates, expenses, payments, journal entries and financial reports) into their own applications, or write records back, using SQL or Entity Framework Core. It runs on .NET 5 to 11 and .NET Framework 4.5 to 4.8 on Windows, Linux and macOS, and the price buys a perpetual developer license with one year of updates.

The typical buyer is the developer asked to "get the FreshBooks numbers into our dashboard" or to sync invoices with an in-house system, who'd rather write SELECT * FROM Invoice WHERE ... than learn FreshBooks' OAuth flow and JSON endpoints.

Quick facts

  • Version: 3.3.248, released November 11, 2026
  • Developer: Devart
  • Data source: FreshBooks, through the current FreshBooks API (called "Alpha" in the provider) or the deprecated Classic API
  • Authentication: OAuth 2.0 with Client Id, Client Secret, Access and Refresh Tokens and Company Name, with automatic token refresh. Classic API uses a URL and authentication token
  • .NET: .NET 5 to 11, .NET Core 2.0 to 3.1, .NET Standard 2.0/2.1, .NET Framework 4.5 to 4.8
  • ORMs: Entity Framework Core 1 to 11, Entity Framework 4 to 6, Dapper, NHibernate
  • Package: Devart.Data.FreshBooks on NuGet, plus a 16.72 MB Windows installer with Visual Studio 2015 to 2026 integration
  • Price: Developer $339.95, Server $799.95, OEM for 10-100 devices $4,999.95, perpetual with one year of updates
  • Trial: 30 days, full product, no card
  • Refunds: within 30 days for technical problems Devart support can't fix
  • What we checked: version 3.3.248 and the 16.72 MB download on Devart's site, the revision history from the first release in February 2016, the connection and token documentation, and the order page on November 14, 2026: $339.95 for the default single-developer license. We didn't connect it to a FreshBooks account.

Download Free TrialBuy Now

Overview

FreshBooks is small-business accounting and invoicing software, popular with freelancers, agencies and service firms. Its data is reachable only through a web API. dotConnect for FreshBooks wraps that API in standard ADO.NET classes (FreshBooksConnection, FreshBooksCommand, FreshBooksDataReader, FreshBooksDataAdapter), so a FreshBooks account behaves like a database your .NET code already knows how to use.

The provider has followed FreshBooks through a platform change. FreshBooks replaced its XML-based Classic API with a new OAuth-based API, and Devart added support for it in version 1.8 in August 2018, recommending everyone switch because the Classic API was deprecated. The connection still has an API Version setting that picks one or the other. Since then the object list has grown a lot: in May 2026 Devart added accounts, adjustment journal entries, credit notes, estimates and 17 report objects, and in September 2026 team members and project rates.

dotConnect for FreshBooks Add Connection dialog with API Version Alpha, Company Name and Web Login button

The FreshBooks data source in Visual Studio's Add Connection dialog: API Version set to Alpha, a Company Name, an Access Token filled in through the Web Login button, and the matching connection string in the code behind.

Features

Accounting objects you can read and write

dotConnect for FreshBooks maps the business records of a FreshBooks company to tables: Client, Invoice, Estimate and EstimateLine, CreditNote and CreditNoteLine, Expense, Item, Payment, Staff, TeamMember, TeamMemberRate and ProjectTeamMemberRate, Account, and AdjustmentJournalEntry with its lines. You query them with SELECT, and insert, update or delete them with ordinary SQL where FreshBooks allows the change.

FreshBooks reports as queryable tables

dotConnect for FreshBooks exposes FreshBooks' built-in reports as objects: ProfitAndLossReport, BalanceSheetReport, CashFlowReport and CashFlowSummaryReport, GeneralLedgerReport and its summary, TrialBalanceReport, TaxSummaryReport, AccountAgingReport, ExpenseDetailsReport, InvoicesReport and InvoiceDetailsReport, PaymentsCollectedReport, ChartOfAccountsReport and the journal-entry reports. That means a finance dashboard can read the same P&L FreshBooks shows its users, instead of recomputing it from raw invoices.

OAuth tokens that refresh themselves

dotConnect for FreshBooks takes care of the most annoying part of the FreshBooks API: its access token expires after 12 hours, and each refresh issues a new refresh token. Point the OAuth Storage option at a text file holding the token pair, and the provider renews the tokens when needed and rewrites the file, so a scheduled job keeps working without anyone signing in again. You can also get tokens interactively with the Web Login button at design time, or through interactive OAuth at runtime since version 3.0.

Deleted records and time zones

dotConnect for FreshBooks has an Include Deleted option that returns records deleted in FreshBooks for the objects that support it (clients, staff, expenses, invoices, items and payments), which matters for audits and for syncs that must notice deletions. A FreshBooks Time Zone setting and a UTC Dates option control how dates are interpreted, so invoice dates don't shift by a day between FreshBooks and your database.

EF Core, Visual Studio and tooling

dotConnect for FreshBooks supports EF Core 1 to 11 (scaffold a model with Scaffold-DbContext), Entity Framework 4 to 6, Dapper and NHibernate. In Visual Studio it adds a Server Explorer data source and design-time components. A FreshBooksLoader component loads rows in bulk, results can be paged, and FreshBooksMonitor with dbMonitor traces the requests your queries generate.

Benefits

  • Financial reporting without re-implementing accounting. Read FreshBooks' own reports rather than rebuilding them from transactions.
  • Unattended jobs that stay authenticated. Token refresh and storage are built in.
  • Joins across FreshBooks objects. Combine clients, invoices and payments in one query, with the local SQL engine doing what the API can't.

Real-World Uses

  • A management dashboard in an ASP.NET Core app shows monthly revenue from ProfitAndLossReport and overdue balances from AccountAgingReport.
  • Invoice creation from a job system: when a project closes in an in-house app, a service inserts an Invoice for the matching Client.
  • Accountant exports: a nightly job copies GeneralLedgerReport and TrialBalanceReport into SQL Server for the year-end file.
  • Agency billing rates: a resourcing tool reads TeamMemberRate and ProjectTeamMemberRate to price staffing plans.

Who It's For, and Who Should Skip It

It's for .NET developers at firms that run on FreshBooks and want its data inside their own software, and for software vendors who build FreshBooks integrations into a .NET product (with the OEM license).

Skip it if you only want FreshBooks numbers in a spreadsheet or BI tool: Devart's Excel Add-in, ODBC driver or SSIS components for FreshBooks fit that better, and FreshBooks itself has app integrations. Skip it if you're on another accounting system (Devart sells separate providers for QuickBooks Online and Zoho Books). And for one or two API calls a month, plain HttpClient code is cheaper.

Usage Guide

  1. Create an app in your FreshBooks developer settings to get a Client Id, Client Secret and redirect URL.
  2. Install the provider (Windows installer, free Devart account) or add the Devart.Data.FreshBooks package from NuGet.
  3. In Visual Studio's Server Explorer, add a FreshBooks Data Source, set API Version to Alpha, enter your Company Name, and click Web Login to authorize and fill in the token.
  4. For a server job, put the access and refresh tokens on two lines of a text file and set OAuth Storage to its path, so the provider can keep them current.
  5. Query with FreshBooksCommand, or scaffold an EF Core model, and add your license key before deploying.

Before you buy

  • Buy Now opens the order page set to one Developer license with a year of updates. Running your integration on a server needs the Server edition ($799.95), and redistributing it needs OEM. You change the edition there, along with 2- or 3-year update terms and premium support.
  • The license is perpetual, so the version you buy keeps working when the update year runs out.
  • Devart's ordering FAQ limits refunds to technical problems its support can't fix within 30 days of purchase, so use the trial against your real FreshBooks company first.

Where it falls short

  • The token setup is still manual for servers. Getting the first access and refresh token pair outside Visual Studio means following Devart's documented steps with a tool like Postman.
  • Not every object supports deleted records or every write. Reports are read-only, and Include Deleted only works where FreshBooks returns deleted rows.
  • Generic marketing copy. Devart's product page talks about "accounts, contacts, leads, and opportunities", CRM terms that don't describe FreshBooks. Check the object list in the trial rather than the sales page.
  • Shared Devart assemblies. All Devart providers share Devart.Data.dll, and mixed versions can block installation. A 2016 forum user hit exactly this.

What Users Say

Review sites carry no rated reviews of dotConnect for FreshBooks itself. The public user record is Devart's forum.

Devart forum, October 2016: an installation problem

A user (redsoxfred) wrote: "I am having real problems installing dotConnect for FreshBooks. I keep getting a message saying The Installer Detected an incompatible version of another Devart product." The leftover came from an Entity Developer trial he had removed, and his connection tested fine but building an Entity Framework model then failed with assembly errors.

Devart's reply (Shalex, Site Admin) was a full clean-reinstall checklist: uninstall the Devart ADO.NET products, remove any Devart.* files left in both Global Assembly Caches and the SharedDlls registry key, clear the Devart program and Visual Studio folders, and reinstall as administrator, plus installing the latest SSDT update for the Microsoft.SqlServer.Types error.

Devart's announcement, August 2018

When the new FreshBooks API arrived, Devart wrote: "We recommend users to switch to the new alpha API, because FreshBooks Classic API is now considered deprecated." It also announced that deleted records could now be queried for "Client, Staff, Expense, Invoice, Item, Payment."

The takeaway: the friction users report is in installation and setup on Windows machines with other Devart products, not in querying FreshBooks. Today's NuGet package sidesteps most of that for projects that don't need the Visual Studio designers.

Comparisons

vs. the FreshBooks API directly

FreshBooks' REST API is free, documented and complete. Writing against it yourself means building the OAuth flow and token refresh, models for each resource, and pagination. dotConnect replaces that with a connection string and SQL. If you need only invoices, go direct. If you need reports, several record types and joins, the provider saves real time.

vs. dotConnect for QuickBooks Online

Same Devart provider family, same price and editions, different accounting system. Choose the one that matches the books your business keeps, and both if you're building a product that must support either.

Editions and Pricing

EditionPriceAllowed use
Developer (Buy Now default)$339.95Development and testing by one developer
Server$799.95Deployment on one server of one organization
OEM for 10-100 devices$4,999.95Shipping the provider inside your own product
Site, OEM for 100+ devicesPriced on the order pageCompany-wide or larger redistribution

FAQs

Does dotConnect for FreshBooks still support the FreshBooks Classic API?

Yes, dotConnect for FreshBooks still has a Classic setting that connects with an account URL and authentication token. FreshBooks deprecated that API, so new projects should use the newer OAuth API (the provider's "Alpha" setting).

How does dotConnect for FreshBooks deal with tokens expiring every 12 hours?

dotConnect for FreshBooks refreshes the access token itself when it expires, and with the OAuth Storage option it saves the new access and refresh tokens to a file, so the next run starts with valid tokens.

Can dotConnect for FreshBooks connect to more than one FreshBooks company?

Yes, one connection per company. dotConnect for FreshBooks selects the company with the Company Name connection parameter, so an app can open separate connections for each business.

Can I protect FreshBooks from accidental changes when using dotConnect?

Yes. dotConnect for FreshBooks has a Readonly connection option that allows only SELECT statements, which suits reporting code.

Does dotConnect for FreshBooks run on Linux?

Yes. dotConnect for FreshBooks runs on Linux and macOS through its NuGet package on .NET 5 to 11 and .NET Core. Version 3.1.33 fixed license-key loading on Red Hat-based distributions.

What do I get after the first year of a dotConnect for FreshBooks license?

dotConnect for FreshBooks keeps working at the version you have. Renewing the subscription gets you newer versions, such as support for new .NET releases and new FreshBooks objects, and continued support.

System Requirements

  • .NET 5 to 11, .NET Core 2.0 to 3.1, .NET Standard 2.0/2.1, or .NET Framework 4.5 to 4.8
  • Windows, Linux or macOS through NuGet. The installer and Visual Studio 2015 to 2026 design-time integration are Windows only
  • A FreshBooks account with a developer app (Client Id and Client Secret)

Conclusion

dotConnect for FreshBooks is worth $339.95 for a .NET developer who has to integrate FreshBooks properly: invoices in, payments out, and real financial reports on a dashboard. Its strongest point is the work it removes around FreshBooks' API, namely OAuth with self-refreshing tokens, plus the 17 report objects that turn FreshBooks' own P&L and balance sheet into query results. The main reason not to buy is a small job: a single invoice sync is easy to write against the API for free, and a server deployment raises the cost to the $799.95 Server edition. Run the 30-day trial against your own FreshBooks company first.

Download Free TrialBuy Now

We may earn a commission when you buy through links on this page.
Copyright © 2026, Ivertech. All rights reserved.