> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sequencehq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Seat events

> View the log of seat update events submitted to Sequence

The seat updates view shows a log of all seat events you have sent to Sequence. Each seat event includes a granular view of the number of seats that were added and removed as well as the new balance (at the time).

Submit seat events via the dashboard for testing.

<Frame>
  <img src="https://mintcdn.com/sequence/kw8O-QAyxJLIUkK_/images/product/seats/seat_events_4.png?fit=max&auto=format&n=kw8O-QAyxJLIUkK_&q=85&s=8e11c70c38c57a96a0372dd7cedb55dd" alt="Send a seat event" width="3248" height="1976" data-path="images/product/seats/seat_events_4.png" />
</Frame>

Use the Seat API to send seat events from your app to Sequence. Below is an example response:

```
{
  "id": "018ef546-b6ee-7370-9202-f21f0b6ddf41",
  "customerSnapshotId": "018ef546-b6ee-7370-9203-7d76d20756b3",
  "customerAlias": "018ef1f0-b892-72ab-bf30-d4db466616c9",
  "seatType": "analyst_seat",
  "sequenceAccountId": "0187338e-c6c4-77be-94ae-387031824db6",
  "snapshotTimestamp": "2024-04-19T00:00:00Z",
  "total": 30,
  "seatChanges": [
    {
      "id": "018ef546-b6fe-7635-a3f8-8c52596d6876",
      "seatSnapshotId": "018ef546-b6ee-7370-9202-f21f0b6ddf41",
      "timestamp": "2024-04-19T00:00:00Z",
      "changeType": "SEAT_ADDED"
    }
```

## How Sequence uses seat events for billing

Each seat event reports the **total** seat balance for a customer and seat metric at a given `eventTimestamp`. Sequence stores every event you submit. When calculating charges, it builds a daily seat timeline from those events.

### Overwriting a seat event

To correct or replace a seat event, resubmit it with the same `customerEventId`. The new submission supersedes the previous event with that ID for billing purposes.

<Note>
  Sequence does not support deleting seat events via the API. Use the same `customerEventId` to overwrite an event you no longer want billed.
</Note>

### Multiple events on the same day

Sequence does not prorate seat changes within a single calendar day.

If you submit two or more seat events for the same customer, seat metric, and calendar day with **different** `customerEventId` values, billing uses the **highest seat count** reported that day.

This means a temporary peak during the day is what billing sees for that day, even if another same-day event (with a different `customerEventId`) reports a lower balance.

<Note>
  All submitted events remain visible in the seat events log. Same-day selection only affects how totals are used when calculating charges.
</Note>

**Example**

| `customerEventId` | Event timestamp | Reported total |
| ----------------- | --------------- | -------------- |
| `seat-update-a`   | 10 April, 09:00 | 13             |
| `seat-update-b`   | 10 April, 16:00 | 15             |
| `seat-update-c`   | 10 April, 18:00 | 12             |

Because these events use different `customerEventId` values, for billing on 10 April Sequence uses **15 seats** (the highest total that day).