---
title: "Owner, handle, plan, live version, warnings, and the calendar connections that need the owner"
method: GET
path: "/api/me"
tags: ["owner"]
---

# Owner, handle, plan, live version, warnings, and the calendar connections that need the owner

`GET /api/me`

## Request

- Base URL: `https://daycal.io`
- URL: `https://daycal.io/api/me`
- Auth: HTTP bearer

## Response `200`

OK

- object
  - `warnings` string[], required
  - `attention` object[], required: Calendar connections that need the owner, most severe first
    - `label` string, required
    - `state` 'limited' | 'expiring' | 'revoked' | 'blocked', required
    - `missing` string[], required: Google scopes the reconnect asks for
    - `reconnectUrl` string, nullable, required: Give it to the owner as is: it opens Daycal, then Google
    - `since` string, date-time, nullable, required
    - `waiting` integer, required: Bookings whose calendar writes wait on this connection

## Other responses

- `401`: Missing, unknown, expired or revoked token: sign in again (RFC 6750 invalid_token)
- `403`: Outside this token's access (RFC 6750 insufficient_scope): the owner scopes are read, write, billing and secrets; the challenge names the ones to sign in again for
- `429`: Rate limited. Retry-After is set when a rate-limit window is spent (not on a booking's own budget)
- `default`: Error

---

[API](https://skmtc.dev/daycal/apis/daycal-api.md) · [All operations](https://skmtc.dev/daycal/apis/daycal-api/llms.txt) · [OpenAPI document](https://skmtc.dev/daycal/apis/daycal-api/revisions/7103ffff4e8c?raw)