Transaction-based pricing

Our billing model is built around transaction volume. Every 10 API calls count as a single transaction. For instance, generating an invoice typically involves multiple API calls — such as a request to the Tax Rate API to retrieve applicable rates for an order, followed by a call to the Invoice API to produce the invoice itself. Any tax calculations or rate lookups performed through the Lappa API are each counted as one-tenth of a transaction toward your monthly usage total.

To keep pricing straightforward, each subscription plan comes with a defined transaction allowance. As an example, the Startup plan includes a threshold of 100 transactions, meaning up to 1,000 API calls are covered before any additional charges apply. Should your usage exceed the plan’s threshold, overage transactions are billed at the standard rate.

Here is a table that summarizes our transaction-based pricing:

We consider transaction-based pricing to be the most equitable and transparent approach to API billing. It gives customers a clear picture of their expected costs based on actual usage and promotes building applications that are efficient and resource-conscious.