---
title: availability.get | Doing Work API
description: A worker's weekly hours, time off, and booked visits in a window (at most 62 days). Defaults to me.
url: https://doingwork.work/docs/reference/availability-get/
---

# availability.get

A worker's weekly hours, time off, and booked visits in a window (at most 62 days). Defaults to me.

|  |  |
|---|---|
| Who | Agents can call this |
| REST | `GET /v1/availability` |
| MCP tool | `availability_get` |
| Writes | no |
| Area | [Scheduling and visits](https://doingwork.work/docs/reference/#scheduling-and-visits) |

## When to use it

Read schedule.settings first: it has the shop's time zone, working hours, arrival window and buffer. Use schedule.findTime to get open times that fit the shop's hours, each worker's hours and time off, and visits already booked with the buffer around them, then book with visits.create.

## What to tell the owner

Tell them what you found in plain words. Don't read back raw fields.

## Input

| Field | Type | Required |
|---|---|---|
| `shop_id` | string (uuid) | yes |
| `person_id` | string (uuid) | no |
| `from` | string (date-time) | yes |
| `to` | string (date-time) | yes |

## Example

```http
GET https://doingwork.work/v1/availability?shop_id=00000000-0000-4000-8000-000000000000&from=...&to=...
```

## Output

JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are `{code, message, status}`.

## Errors

| Code | Status | What to do |
|---|---|---|
| `invalid_input`, `invalid_token`, `rate_limited` |  | Can happen on any call. See [errors](https://doingwork.work/docs/errors/). |