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.

WhoAgents can call this
RESTPOST /v1/service-due
MCP toolservices_addDue
Writesyes, send an Idempotency-Key
AreaShop

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

FieldTypeRequired
shop_idstring (uuid)yes
customer_idstring (uuid)yes
job_idstring (uuid)no
titlestringyes
due_onstring (date)yes
repeat_monthsintegerno

Example

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

CodeStatusWhat to do
invalid_input, invalid_token, rate_limitedCan happen on any call. See errors.