:::endpoint GET /v1/me/calendar/tags

What an editor offers when somebody puts a label on an appointment. The labels
belong to the workspace, so the same label means the same thing in every
calendar, and every appointment already carries its own whole in `tags`. They
are made and renamed on the website.

Send the ids as `tag_ids` when [creating](/docs/api/calendar/create) or
[changing](/docs/api/calendar/update) an appointment.

## Request

```bash
curl https://api.proppertrading.com/v1/me/calendar/tags \
  -H "Authorization: Bearer ptat_9f2c1a44_3b8e7d2f5c9a1b4e6d8f0a2c4e6b8d1f"
```

## Response

```json
{
    "data": [
        { "id": "ctag_f7k3w9n2b5r8m4tx", "object": "calendar_tag", "name": "Onboarding", "color": "emerald" },
        { "id": "ctag_h2v6d9s4p8c3y7qe", "object": "calendar_tag", "name": "Payouts", "color": "amber" }
    ],
    "meta": { "request_id": "req_01kz4bkr1aj1gv63d8fv3133ey" }
}
```

In the order the workspace put them in. Empty where the workspace has none.

## Errors

| Status | Code                     | Meaning                                    |
| ------ | ------------------------ | ------------------------------------------ |
| 403    | `insufficient_scope`     | This device does not hold `calendar:read`  |
| 403    | `calendar_not_permitted` | The account may not open a calendar at all |