# `frontline meetings`

Meeting analytics across the whole account. Works with an account API key, or a user key belonging to an OWNER or ADMIN. The notetaker defaults every user inherits are `frontline settings meetings`; a user's own meetings live in the `max meetings` command.

```bash
frontline meetings [options] [command]
```

## `frontline meetings analytics`

Meeting volume and duration across the account, broken down by platform, source and user. Covers everyone; for one person's own numbers, use `max meetings analytics`.

```bash
frontline meetings analytics [options]
```

**Options**

| Flag | Description | Default |
|  --- | --- | --- |
| `--start-date <date>` | Only meetings on or after this date |  |
| `--end-date <date>` | Only meetings on or before this date |  |
| `--user-ids <ids>` | Comma-separated user ids to narrow the report to |  |
| `--team-ids <ids>` | Comma-separated team ids to narrow the report to |  |
| `--api-key <key>` | Override API key for this run (else FRONTLINE_API_KEY env, else stored profile key) |  |
| `--base-url <url>` | Advanced: override Public API base URL for this run |  |
| `--profile <name>` | Credentials profile: uses that profile's saved API key and Public API base URL (see `frontline auth profiles list`) |  |
| `--debug` | Show debug info on stderr (token is redacted) |  |
| `--pretty` | Pretty-print human-readable output (instead of default JSON) |  |
| `--table` | Render list results as a table (implies --pretty) |  |
| `--json` | Output raw JSON (default behavior — accepted as a no-op) |  |