---
title: "Connect module: events.push"
description: How your platform pushes players, transactions and sessions into OneHazel, and how the module becomes conformant.
---

For the operator's engineer sending player and activity data to OneHazel.

# events.push

The events.push module is the data feed from your platform into OneHazel: player records, deposits, bets, sessions and state changes. Vendors that score, report on or react to player activity (KYC, responsible gaming, affiliate reporting, analytics) read from it.

## Who calls whom

You call OneHazel, through the Operator Data API at `https://api.onehazel.com/operator-data-api`. The endpoints, batch sizes and payload shapes are documented under [Data Ingestion](/data-ingestion/): [entities](/data-ingestion/entities), [events](/data-ingestion/events), [states](/data-ingestion/states) and [batch operations](/data-ingestion/batch).

## Headers

`Authorization: Bearer <your OneHazel API key>`, an `oh_live_` key. There is no request signature on this direction. Keep the key on your server.

## How it becomes conformant

The events.push module has no conformance run. Its state is derived from a recorded signal: it becomes `conformant` the first time OneHazel receives an entity or an event from you, and stays so. Until then `connect_status` shows it `not_started` with the reason "push a first entity or event". Data from the demo casino simulator does not count. Its `evidence` is always `derived`.

## Conformance

None. The first real push is the check.

## Samples

The Connect samples cover only the modules you host. For pushing data, the request examples on the [Data Ingestion](/data-ingestion/) pages are the starting point.