Dokumentation

Blog

Authorization

Fynn Docs

Integrationen

API Referenz

Changelog

App Login

Termin buchen

Support

Measurements are used to define the *amount of a unit that is used* for the price calculation.
*SaaS Product Examples*
 * User: the amount of users that are allowed to use the software.
 * Member: the amount of members that are allowed to use the software.
 * Environment: the amount of environments that are allowed to use the software.

*Hosting Examples*
 * CPU: the amount of CPU cores that are used.
 * RAM: the amount of RAM that is used.
 * Storage: the amount of storage in GB that is used.
 * Traffic: the amount of traffic in GB that is used.

 * The aggregation type defines *how the amount of units is calculated* during a billing interval.
 * The unit defines *what is measured*.

The aggregation types are useful to be more flexible in the billing process.
Imagine you sell a product with user seats, but you want to bill the customer for the maximum amount of users that were active during the billing interval.
In this case you would use the aggregation type "max".
If you want to bill the customer for the sum of all users that were active during the billing interval, you would use the aggregation type "sum".
If you want to bill the customer for the average amount of users that were active during the billing interval, you would use the aggregation type "avg".

The aggregation type also depends how and when you push the measurements to the API. Feel free to contact us if you need help.


The aggregation type of the measurement. Describes how the quantity is calculated. This cannot be changed after creation, otherwise it would change the whole calculation for existing subscriptions.

Possible values:
 * `count`: The number of sent measurements in the billing interval. Metered usage, which resets to 0 after each billing interval.
 * `count_unique`: The number of unique sent measurements in the billing interval, identified by the id given on event creation.
 * `max`: The maximum value of all sent measurements in the billing interval. Metered usage, which resets to 0 after each billing interval.
 * `sum`: The sum of all sent measurements in the billing interval.
 * `last_value`: The last sent measurement.
 * `average`: The average of all sent measurements in the billing interval.

A unique code which can be used to identify the measurement.

A description of the measurement, which is shown in the summary of the usage data in the invoice.

If set to false, the measurement will be billed for the whole billing interval, even if the quantity changes, or the item is cancelled / terminated during the billing interval.

The type of the measurement. This cannot be changed after creation, otherwise it would change the whole calculation for existing subscriptions.

Possible values:
 * `instant_metered`: The measurement value is reset to 0 after each push. The measurement gets billed immediately and an invoice is created. The aggregation type must be "last_value".
 * `metered`: The measurement value is reset to 0 after each billing interval.
 * `recurring`: The measurement value is not reset to 0 after each billing interval and the last value is used for all following billing intervals. The aggregation type must be "last_value".

The date and time when the resource was created.

The date and time when the resource was last updated.

Get all measurements.

<sup>Required permissions: `measurement:read`</sup>

Get all measurements.

Willkommen bei Fynn! Hier findest du alles, was du brauchst, um loszulegen.

Willkommen 👋

Richte deine Organisation ein, um mit der Abonnementabrechnung zu beginnen.

Erste Einrichtung

Organisation einrichten

Benutzer verwalten

Nummernkreise

Passe das Aussehen an deine Unternehmensfarben und Design an.

Aussehen

Währungen verwalten und automatisch umrechnen

Währungen

Zahlungsmethoden

Konfiguriere Benachrichtigungen und E-Mails.

Benachrichtigungen

Passe die Web-Oberfläche an, um Arbeitsprozesse zu optimieren.

Web-Oberfläche

Web-Oberfläche anpassen

Erstelle benutzerdefinierte Attribute für verschiedene Objekte.

Benutzerdefinierte Attribute

Welcome to the API reference documentation for the Fynn API.

Getting started

All API endpoints are authenticated using Bearer tokens and picked up from the specification file.

Authentication

Learn how to manage payment methods on your own payment page.

Manage payment methods on your own payment page

Collect usage data

Learn how to enable manual invoice checks for all customers.

Enable manual invoice checks

Wir bieten dir eine Vielzahl von Integrationen zu 3rd-Party-Tools und -Services, um die Funktionalität der Fynn-Plattform zu erweitern.

Übersicht

GoCardless

Stripe Payments

PayPal

SEPA-Lastschrift

Überweisung

DATEV ist eine Software für Steuerberater und Unternehmen.

DATEV

HubSpot

Kunde verwalten

Kundenbereich

Einheiten

Erstelle und verwalte deine abrechenbare Einheiten

Abrechenbare Einheiten verwalten

Lerne die verschiedenen Arten von Typen verstehen

Wiederkehrend vs nutzungsbasiert

Erstelle und verwalte deine Produkt Kategorien

Produkt Kategorien

Produkte

Add-Ons

Lerne den Unterschied zwischen Vorauszahlung und Nachzahlung kennen

Vorauszahlung vs Nachzahlung

Lerne wie Proratierung in der Fynn Plattform funktioniert.

Proratierung

Abonnements verwalten

Rechnung erstellen

Rechnung stornieren

Rechnung herunterladen

Gutschrift erstellen

Zahlung hinzufügen

Automatisiertes Mahnwesen für Rechnungen

Mahnwesen

Zahlungen

Dashboard

Reporting

Angebote

Lerne wie du einen Checkout Link erstellst und an deine Kunden sendest.

Checkout Link

Erstelle und verwalte Gutscheine und Rabatte.

Gutscheine & Rabatte

Buchhaltungseinstellungen und Integrationen konfigurieren.

API documentation

User

Tenant

User & permissions

Settings

Payment

Analytics

Customer

Billing

Dunning

Subscription

Offers

Catalogue

Checkout

Accounting

Taxes

Get all measurements

Authorizations

Query Parameters

Response