# Key logs

A Key Log records a guest's granted access to a Product where the
  receiver is identified by an email, phone number, or license plate
  rather than an app account. It is backed one-to-one by an Operation
  Token, which holds the actual validity window and the signed
  open/close/status credentials used to remotely operate the device, so
  a key log's status and dates are driven by its token. Key logs can be
  resent, bulk-updated, or blocked by the sender.

- [Get all key logs](https://docs.parklio.com/api/endpoints/key-logs-find-all.md): `GET /v2/key-logs`
- [Bulk update key logs](https://docs.parklio.com/api/endpoints/key-logs-bulk-update.md): `PATCH /v2/key-logs`
- [Get all key invitation receiver emails](https://docs.parklio.com/api/endpoints/key-logs-receiver-emails.md): `GET /v2/key-logs/receiver-emails`
- [Get key logs](https://docs.parklio.com/api/endpoints/key-logs-find-one.md): `GET /v2/key-logs/{id}`
- [Update key logs](https://docs.parklio.com/api/endpoints/key-logs-update.md): `PATCH /v2/key-logs/{id}`
- [Delete key logs](https://docs.parklio.com/api/endpoints/key-logs-remove.md): `DELETE /v2/key-logs/{id}`
- [Resend key logs](https://docs.parklio.com/api/endpoints/key-logs-resend.md): `POST /v2/key-logs/resend`