---
title: "Report usage events"
method: POST
path: "/api/v1/events"
tags: ["Usage"]
---

# Report usage events

`POST /api/v1/events`

Reports raw usage events for event-based metering. Events are ingested asynchronously and aggregated into usage totals.

## Headers

- `X-ACCOUNT-ID` string
- `X-ENVIRONMENT-ID` string

## Request body

- ReportEventRequestDto — Report raw usage events. Batch up to 1000 events with dimensions.
  - `events` object[], required — A list of usage events to report
    - `eventName` string, required — The name of the usage event
    - `customerId` string, required — Customer id
    - `resourceId` string, nullable — Resource id
    - `timestamp` string, date-time — Timestamp
    - `idempotencyKey` string, required — Idempotency key
    - `dimensions` object — Dimensions associated with the usage event

## Response `202`

Confirmation that events were accepted for processing.

- EventResponseResponseDto — Response object
  - `data` object, required — Empty success response confirming that events were successfully ingested and queued for processing by Stigg's metering system.

## Other responses

- `400` — bad request.
- `401` — User is not authenticated.
- `403` — User is not allowed to access this resource.
- `404` — Event not found.
- `429` — Too many requests.

---

[API](https://skmtc.net/stiggio/apis/stigg-api.md) · [All operations](https://skmtc.net/stiggio/apis/stigg-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/stiggio/stigg-api/versions/ffc977f1c07e/schema)