Skip to main content

· One min read

It is now possible to assign multiple plans to a customer (e.g. if your customer needs to create several workspaces on your platform, you can link a plan to each workspace).

To help differentiate each plan, you can add display names that will appear in the user interface and on invoices.

Kindly note that:

  1. All plans must be denominated in the same currency; and
  2. You must now specify the subscription_id for each event or create batch events.

Click here to see the documentation

· One min read

To help us better understand your needs, we have added a tracking module to the self-hosted version of Lago.

Data analytics will help us improve the quality of our product and performance of the API.

As the privacy of our users is of paramount importance, we will not collect any personal information about your customers or the amount of your invoices, and you can opt out at any time.

Learn more

· 2 min read

We like our users when they use our nice and clean UI, but we also love when they use our API. One of the usecase could be to use Lago as a white-labeled solution.

Here is the full list of endpoints we have just released:

Billable metrics

  • Create a billable metric POST /api/v1/billable_metrics
  • Update a billable metric PUT /api/v1/billable_metrics/:code
  • Destroy a billable metric DELETE /api/v1/billable_metrics/:code
  • Fetch a specific billable metric GET /api/v1/billable_metrics/:code
  • Fetch all billable metrics GET /api/v1/billable_metrics?per_page=2&page=1

Plans

  • Create a plan POST /api/v1/plans
  • Update a plan PUT /api/v1/plans/:code
  • Destroy a plan DELETE /api/v1/plans/:code
  • Fetch a specific plan GET /api/v1/plans/:code
  • Fetch all plans GET /api/v1/plans?per_page=2&page=1

Coupons

  • Create a coupon POST /api/v1/coupons
  • Update a coupon PUT /api/v1/coupons/:code
  • Destroy a coupon DELETE /api/v1/coupons/:code
  • Fetch a specific coupon GET /api/v1/coupons/:code
  • Fetch all coupons GET /api/v1/coupons?per_page=2&page=1

Add-ons

  • Create a add_on POST /api/v1/add_ons
  • Update a add_on PUT /api/v1/add_ons/:code
  • Destroy a add_on DELETE /api/v1/add_ons/:code
  • Fetch a specific add_on GET /api/v1/add_ons/:code
  • Fetch all add_ons GET /api/v1/add_ons?per_page=2&page=1

Current usage

  • Get the current usage of a specific customer GET /api/v1/customers/:customer_id/current_usage

Organization

  • Update the information of your organization PUT /api/v1/organizations

· One min read

It is now possible to check the version of the Lago application you are using.

Click the name of your organization in the top-left corner of the user interface to see the app version currently in use.

App version as displayed in the user interface

· One min read

Current Usage

Good news for those who follow closely the consumption of their customers. You can now track the current billing usage of your customers either from the UI or from the API.

To access this Usage tab:

  1. Access your list of customers;
  2. Select a specific customer that is already linked to a subscription;
  3. Access the usage tab; and
  4. Get a complete view of usage-based consumption that is going to be billed on the next invoice.

On top of that, you can fetch the current usage of a customer directly from the API. To do so, you can access the following endpoint GET /api/v1/customers/:customer_id/current_usage

· One min read

Lago will generate a PDF file for each new invoice.

You can download invoices via the user interface or the API and can also modify some of the elements included in the invoice template.

Full documentation available here.

· One min read

Lago now offers native integration with Stripe, including (but not limited to):

  • Ability to create Lago customers in Stripe automatically and retrieve their customer ID;
  • Ability to define Stripe as the default payment provider for a customer;
  • Ability to generate payment intents automatically;
  • Ability to update the status of an invoice depending on the payment status; and
  • Ability to receive a webhook when a payment fails.

To learn more about this integration, please consult our guide.

· One min read

When setting up a plan, you can select the weekly interval to define a weekly billing period.

The plan interval applies to the subscription and charges, which means that:

  • For plans that must be paid in advance, the subscription fee is invoiced at the beginning of the week;
  • For plans that are paid in arrears, the subscription fee is invoiced at the end of the week; and
  • Usage is calculated at the end of each week.

The week starts on Sunday and ends on Saturday. If the customer's subscription starts in the middle of the week, the fees will be applied on a pro-rata basis.

· One min read

Before the release of this feature, usaged-based features (charges) were following the plan period. If the plan period was invoiced yearly, the charges were invoiced yearly.

It's now possible to invoice billable metrics on a montly basis for a plan billed yearly. The base amount of the plan will be invoice yearly (in-arrears or in-advance), but your usage based features will be invoiced on a monthly basis.

To do so:

  1. Access a Plan;
  2. Define a plan yearly;
  3. Price additional charges from your billable metrics; and
  4. Turn on the toggle for applying charges monthly.

By switching on, all the charges will be invoiced monthly even if the plan is yearly.

tip

The last invoice is gathering both the subscription and the usage-based charges

charges invoiced monthly

· One min read

Inside the Plans, by creating a charge, you can now select the percentage charge model.

This feature is pretty useful for industries willing to take a % + fixed fee out of a usage-based features (for banking or charity industry, for instance). These fees are applied on the units to be charged (e.g. the aggregation result of your billable metric).

The fixed charge can either be applied per each single unit or for all units.

Percentage charge

· One min read

You are now able to view all the ingested events sent from your application to Lago. We called this feature debugger because it makes the event ingestion easier and more understandable.

  1. Access the Developer sidebar item;
  2. Click the Debugger tab; and
  3. Take a look at the latest events ingested
tip

If an event you sent is not shown in the UI, it means that it has not been ingested by Lago

This debugger is also helpul to warn you for 2 specific cases:

  1. Warning 1 - The event code is not related to an existing billable metric
  2. Warning 2 - The property sent does not match the aggregation property defined in your billable metric

Debugger

· One min read

Add-ons are now available on Lago. Create add-ons to apply one-time fees (e.g. setup fee, one-time purchase, etc.) and generate the corresponding invoices instantly.

Full documentation available here.

· One min read

We've added a new template to our collection: click here to learn how to replicate Algolia's pay-as-you-go pricing.

It's a great starting point for companies whose pricing fully depends on usage, such as cloud service providers and API companies.

With Lago, you can adapt this template to your products and services, using some of our most popular features, including the 'sum' aggregation type and the package charge model.

· One min read

Introducing coupons, a new feature that allows you to offer discounts to your customers.

Full documentation available here.

· One min read

You can now modify the subscription assigned to a customer through the user interface.

To learn how to upgrade or downgrade a subscription and how it affects billing, please refer to the documentation.

· One min read

It is now possible to apply a package pricing model to a charge. To do so:

  1. Select an existing plan (or create a new one);
  2. Add a charge; and
  3. Select the package pricing model.

This new pricing model allows you to apply a flat fee to a range of units. The price will be fixed for the entire range, regardless of the number of units consumed by the customer during the billing period.