services.completeDue
Mark a service due date done (owner or office). If it repeats, the next one is created repeat_months after the date the service was done (today in the shop's time zone unless done_on is given) and returned as next.
| Who | Agents can call this |
| REST | POST /v1/service-due/complete |
| MCP tool | services_completeDue |
| Writes | yes, send an Idempotency-Key |
| Area | Shop |
When to use it
Mark a service due date done (owner or office). If it repeats, the next one is created repeat_months after the date the service was done (today in the shop's time zone unless done_on is given) and returned as next.
What to tell the owner
Say what you did in plain words and what happens next.
Input
| Field | Type | Required |
|---|---|---|
service_due_id | string (uuid) | yes |
done_on | string (date) | no |
Example
POST https://doingwork.work/v1/service-due/complete
content-type: application/json
Idempotency-Key: 3f1c...
{
"service_due_id": "00000000-0000-4000-8000-000000000000"
}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. |