visits.create
Book a visit to a job at a time, optionally with the workers going (assignee_ids, a saved crew_id, or both). Overlaps for those workers come back in conflicts.
| Who | Agents can call this |
| REST | POST /v1/visits |
| MCP tool | visits_create |
| Writes | yes, send an Idempotency-Key |
| Area | Scheduling and visits |
When to use it
Book a visit to a job at a time, optionally with the workers going (assignee_ids, a saved crew_id, or both). Overlaps for those workers come back in conflicts.
What to tell the owner
Say what you did in plain words and what happens next.
Input
| Field | Type | Required |
|---|---|---|
job_id | string (uuid) | yes |
starts_at | string (date-time) | yes |
ends_at | string (date-time) | yes |
title | string | no |
notes | string | no |
assignee_ids | array | no |
crew_id | string (uuid) | no |
arrival_window_minutes | integer | no |
priority | string (one of normal, urgent, emergency) | no |
Example
POST https://doingwork.work/v1/visits
content-type: application/json
Idempotency-Key: 3f1c...
{
"job_id": "00000000-0000-4000-8000-000000000000",
"starts_at": "...",
"ends_at": "..."
}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. |