Events - Nozle

Overview

Application Workflows

Billing Resources

Usage & Metering

Invoicing & Payments

Platform & Operations

Use the Node.js or Python SDK for event ingestion. The SDK sends one event per track() call; it does not batch automatically.

See Node.js event tracking or Python event tracking for subscription resolution and idempotency behavior.

Event envelope

{
  "event": {
    "transaction_id": "request_0183f",
    "external_customer_id": "customer_123",
    "external_subscription_id": "subscription_123",
    "code": "api_calls",
    "properties": {
      "model": "example-model",
      "tokens": 1500
    },
    "timestamp": "2026-08-04T10:30:00Z"
  }
}

Field	Required	Description
`transaction_id`	yes	Stable identifier for the logical event. Preserve it with the same timestamp on retries.
`external_customer_id`	yes	Customer that generated usage.
`external_subscription_id`	recommended	Subscription receiving usage. Required when resolution would be ambiguous.
`code`	yes	Feature code.
`properties`	no	Aggregation and attribution metadata.
`timestamp`	no	ISO 8601 occurrence time.

For direct HTTP ingestion, send this envelope to the Events API configured for your organization with a secret key. Prefer the SDKs so subscription lookup, UUID generation, timeout handling, and errors remain consistent.

For retry safety, preserve the complete event identity. High-volume event storage deduplicates using both transaction_id and timestamp.

​Event envelope

Event envelope