API reference

Update a confirmation

Change an order after it's created: a new delivery date or window, the items, the address, the customer's details and more.

PATCH/v1/confirmations/{id}

Orders change: the delivery moves, the customer gives a new number, an item is swapped. Send only what's changed. Objects merge with what's there; arrays, such as order.items and order.rescheduleOptions, are replaced whole. The result is checked exactly like a create, so the same validation errors apply.

curl -X PATCH https://api.anyonein.co.uk/v1/confirmations/cf_7d2a9c41e0b3f658 \
  -H "Authorization: Bearer $ANYONEIN_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "order": { "date": "2026-10-20", "window": { "from": "12:00", "to": "16:00" } } }'

const res = await fetch('https://api.anyonein.co.uk/v1/confirmations/cf_7d2a9c41e0b3f658', {
  method: 'PATCH',
  headers: { Authorization: `Bearer ${process.env.ANYONEIN_KEY}`, 'Content-Type': 'application/json' },
  body: JSON.stringify({ order: { date: '2026-10-20', window: { from: '12:00', to: '16:00' } } }),
});
const { confirmation } = await res.json(); // status "scheduled", with a new plan for the new day

res = requests.patch(
    "https://api.anyonein.co.uk/v1/confirmations/cf_7d2a9c41e0b3f658",
    headers={"Authorization": f"Bearer {os.environ['ANYONEIN_KEY']}"},
    json={"order": {"date": "2026-10-20", "window": {"from": "12:00", "to": "16:00"}}},
    timeout=15,
)
confirmation = res.json()["confirmation"]

<?php
$ch = curl_init('https://api.anyonein.co.uk/v1/confirmations/cf_7d2a9c41e0b3f658');
curl_setopt_array($ch, [
    CURLOPT_CUSTOMREQUEST => 'PATCH',
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => ['Authorization: Bearer ' . getenv('ANYONEIN_KEY'), 'Content-Type: application/json'],
    CURLOPT_POSTFIELDS => json_encode(['order' => ['date' => '2026-10-20', 'window' => ['from' => '12:00', 'to' => '16:00']]]),
]);
$confirmation = json_decode(curl_exec($ch), true)['confirmation'];

What you can change

orderobjectoptional: Any of date, window, items, address, notes, ref, type, service, requiresSignature and rescheduleOptions.
customerobjectoptional: Any of name, first, phone and email.
channels, `smsVia`, `voice`, `cadence`, `brand`, `webhookUrl`, `externalId`optional: As on create.

Anything else, such as status or outcome, can't be set and returns a 422.

What happens

You change	What AnyoneIn does
`order.date` or `order.window`	Starts a fresh plan for the new slot. Any answer the customer already gave is kept in `history`, `outcome` goes back to `null`, `status` to `scheduled`, and the customer is contacted again about the new day. You get a `confirmation.updated` webhook
`channels` or `cadence`	Starts a fresh plan the same way
Anything else (address, items, notes, contact details)	Changes it in place. The plan and any outcome stay as they are, and the next message uses the new details

If the customer has opted out, a new date is recorded but they aren't contacted, and the confirmation stays action_needed with an opt_out outcome.

Returns

200 OK with the updated confirmation, and warnings if anything you sent was dropped or adjusted.

Errors

Status	`code`	When
`404`	`not_found`	No confirmation with that `id` for this key
`409`	`conflict`	It's cancelled (create a new one), or a call to the customer is in progress (try again in a few minutes)
`422`	`validation_failed`	A field isn't valid, the new date is in the past, or the field can't be changed

Base URL https://api.anyonein.co.uk/v1, for test and live keys alike. Found a mistake? Tell us.

#What you can change

#What happens

#Returns

#Errors

What you can change

What happens

Returns

Errors