# List what was sent for one event

Every invitation, update, cancellation and reply this identity sent for the event, and what became of each delivery: delivered, sent, being retried, refused, rejected by the remote server, or never sent and why. Owner-only.

## `GET /api/v1/identities/{identityId}/calendars/{calendarId}/objects/{href}/scheduling`

### Path parameters

- `identityId` (string, required) — Mailbox identity ULID
- `calendarId` (string, required) — Collection ULID or its name slug
- `href` (string, required, 1–512 chars) — The object's href: its filename segment within the collection (e.g. 1a2b3c.ics)

### Query parameters

- `limit` (integer, ≥ 1, ≤ 500) — Rows, the latest ones (default and max 500)

### Responses

**200** — The event's outbound scheduling record, oldest first

`application/json` → ObjectSchedulingLog

- `entries` (object[], required) — Oldest first, the latest 500 at most. Kept 14 days like every scheduling log row; the SCHEDULE-STATUS on the event outlives them
  - `counterpart` (string, required) — The recipient's address, lowercased
  - `createdAt` (integer <int64>, required) — When it was recorded, unix seconds
  - `id` (string, required) — Row ULID
  - `method` (string, required) — iTIP METHOD this store sent: REQUEST, CANCEL or REPLY
  - `outcome` (string | null, required) — delivered (written into a calendar on this platform), sent (handed to the relay), retryable (being retried), refused, failed (a remote server refused it after the relay took it) or skipped (never sent: a group or webhook address, one the organizer may not invite, a delegate's remote send, SCHEDULE-AGENT=CLIENT)
  - `reason` (string | null, required) — Why, when the outcome was not a delivery; for a remote failure, the remote server's reply
  - `status` (string | null, required) — The RFC 6638 SCHEDULE-STATUS this result stamped (1.0, 1.1, 1.2, 3.7, 3.8, 5.1, 5.2, 5.3), or null
- `uid` (string, required) — The event's UID

**401** — unauthorized: the bearer credential is missing, malformed, expired, or revoked. Carries a `WWW-Authenticate: Bearer` challenge

`application/json` → ErrorBody

**404** — No such object, collection, or mailbox, or not this principal's own

`application/json` → ErrorBody

**503** — temporary_failure: the platform's storage could not answer just now; retry after the Retry-After window. Any operation can answer this. A write that got it may have been applied, so retry it with the same idempotency key where it takes one, or read the state back first (see Transient failures in the API description)

`application/json` → ErrorBody

### Example request

```bash
curl -X GET 'https://api.open.email/api/v1/identities/{identityId}/calendars/{calendarId}/objects/{href}/scheduling' \
  -H 'Authorization: Bearer oek_…'
```