Reschedule Booking

Purpose

Gives an existing booking a new date, identified by its Sodtrack id.

The request carries the same dateAssignment object used when creating bookings, with the same meaning for each type: direct schedules the booking to a specific date and time, userScheduling removes the date and hands the choice back to the customer, providerScheduling removes the date and asks the provider to propose one, and onDemand turns the booking into an on-demand service to be executed as soon as possible.

This endpoint does not validate coverage or agenda availability. It writes the date as sent. Verify beforehand that the booking's address is covered and that the provider has the requested slot, using the coverage and availability endpoints, so that this call stays cheap and predictable.

Authentication

The endpoint is restricted to Sodtrack's private integration network. Requests from unauthorized origins are rejected.

Endpoint

PATCH /api/integration/booking/{bookingId}/reschedule

Field Definitions

🧩 Path parameters

🕒 Date assignment (dateAssignment)

Example Request

Reschedule to a specific date and time:

{
  "dateAssignment": {
    "type": "direct",
    "date": "2026-10-15T09:00:00.000Z"
  }
}

Hand the date back to the customer:

{
  "dateAssignment": {
    "type": "userScheduling"
  }
}

Turn the booking into an on-demand service:

{
  "dateAssignment": {
    "type": "onDemand"
  }
}

Ask the provider to propose a date:

{
  "dateAssignment": {
    "type": "providerScheduling"
  }
}

Reschedule to a date within a time range:

{
  "dateAssignment": {
    "type": "direct",
    "date": "2026-10-15T09:00:00.000Z",
    "timeRange": {
      "type": "timeRangeId",
      "value": 5
    }
  }
}

Response Example

The updated booking, in the same shape as the booking search and detail endpoints.

{
  "id": 13,
  "reference": "BK-2026-0456",
  "status": "accepted",
  "scheduledDate": "2026-10-15T09:00:00.000Z",
  "quantity": 1,
  "totalDurationMinutes": 60,
  "doneDate": null,
  "createdDate": "2026-08-26T04:22:29.911Z",
  "customer": {
    "id": 32841,
    "reference": "CUST-00123"
  },
  "stakeholder": null,
  "service": {
    "id": 1,
    "name": "Water heater installation"
  },
  "variant": {
    "id": 1,
    "name": "Standard installation",
    "type": "execution",
    "skus": []
  },
  "category": {
    "id": 1,
    "name": "Installations"
  },
  "address": {
    "formattedAddress": "Av. Corrientes 1234, Buenos Aires",
    "coordinates": null
  },
  "originAddress": null,
  "saleChannel": null,
  "project": null,
  "lead": null,
  "provider": {
    "id": 19,
    "reference": null,
    "name": "Carlos",
    "lastname": "Muñoz",
    "email": "carlos.munoz@example.com",
    "phone": "+56972345678",
    "identificationNumber": null,
    "assignedTo": null
  },
  "bookingBundle": null,
  "price": 0,
  "cost": 0,
  "bookingAddOns": [],
  "products": [],
  "incidents": [],
  "alerts": [],
  "notes": [],
  "dynamicFormSnapshotFields": []
}

Response Fields

Error Responses

Business Rules & Constraints

No coverage or availability validation

Sodtrack does not check that the booking address is covered, nor that the assigned provider is available at the requested date, time or time range. The date is written as sent. Run those checks first with the coverage and availability endpoints; this endpoint is meant to be the final, cheap write once a valid slot is known.

What each type does

Date, time and time range

The day and the time of day are both taken from dateAssignment.date, kept as the exact instant sent: 2026-10-15T09:00:00.000Z and 2026-10-15T06:00:00-03:00 schedule the same moment. When timeRange is sent, the matching time range is recorded as the booking's period window; the time of day is not moved into the range. When timeRange is omitted, any period previously recorded on the booking is cleared.

Which bookings can be rescheduled

Bookings with status on_my_way_to_origin, arrived_to_origin, on_my_way_to_destination, arrived_to_destination, left_destination, done or cancelled are rejected. Any other status is accepted, including bookings that never had a date.

Status after the reschedule

If the booking was waiting for a provider-proposed date, the pending proposals are cancelled.

Bundled bookings

Rescheduling a booking that belongs to a bundle reschedules the whole bundle: the new date is applied through the bundle head, and every booking in the bundle follows it.

Side effects

The reschedule is logged on the booking, the reminder cycle restarts, the provider's agenda is updated when one is assigned, and the usual booking-scheduled and status-change notifications are sent to your configured webhooks.