---
title: services.addDue | Doing Work API
description: Record when a customer's next service is due (owner or office), for example a yearly furnace tune-up. Give a title, the due date and optionally repeat_mont
url: https://doingwork.work/docs/reference/services-adddue/
---

# services.addDue

Record when a customer's next service is due (owner or office), for example a yearly furnace tune-up. Give a title, the due date and optionally repeat_months so marking it done sets the next one. If the shop has service due emails on, the customer gets one reminder email before the date.

|  |  |
|---|---|
| Who | Agents can call this |
| REST | `POST /v1/service-due` |
| MCP tool | `services_addDue` |
| Writes | yes, send an Idempotency-Key |
| Area | [Shop](https://doingwork.work/docs/reference/#shop) |

## When to use it

Record when a customer's next service is due (owner or office), for example a yearly furnace tune-up. Give a title, the due date and optionally repeat_months so marking it done sets the next one.

## What to tell the owner

Say what you did in plain words and what happens next.

## Input

| Field | Type | Required |
|---|---|---|
| `shop_id` | string (uuid) | yes |
| `customer_id` | string (uuid) | yes |
| `job_id` | string (uuid) | no |
| `title` | string | yes |
| `due_on` | string (date) | yes |
| `repeat_months` | integer | no |

## Example

```http
POST https://doingwork.work/v1/service-due
content-type: application/json
Idempotency-Key: 3f1c...

{
  "shop_id": "00000000-0000-4000-8000-000000000000",
  "customer_id": "00000000-0000-4000-8000-000000000000",
  "title": "...",
  "due_on": "..."
}
```

## 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/). |