Skip to main content
Usage events are the foundation of usage-based billing. Send them from your application to track customer consumption.

Quick Start

Send a usage event:

Event Structure

Each event requires these fields:
The customerId field accepts both the Fynn UUID and the customer’s externalId. Fynn automatically detects which format is being used.

Example: AI Token Usage

Example: API Call Tracking


Batch Import

Send up to 1000 events in one request:

Response

Success (202 Accepted):
Partial Success:

Idempotency

Events with the same transactionId are only processed once. If you send the same event twice, Fynn returns the existing event instead of creating a duplicate.
Use deterministic transaction IDs, e.g.: ${customerId}-${timestamp}-${eventName} or UUIDs.

Properties for Nutzungsmetriks

The properties object should contain all fields your Nutzungsmetriks need:

Grouping Properties

If your Nutzungsmetrik uses groupBy, include those fields:

Filter Properties

If your Nutzungsmetrik has filters, include the filtered fields:

Legacy: Subscription Measurements

For existing integrations using subscription-based measurements:
See: API Reference

Best Practices

Timestamps

Always use UTC in ISO 8601 format:

Batch Sizes

Error Handling