Reschedule a session

Overview

Update the meeting timestamp and refresh related scheduling work. The timestamp identifies an exact instant. This operation does not reserve a notary’s availability; confirm the appointment with the intended participants.

1. Agree a new time

   Confirm the intended local date, time, and timezone.

2. Convert and update

   Generate the correct offset and send session_timing.

3. Confirm downstream effects

   Check reminders, notifications, and any open-call schedule.

Parameters

Request example

Use a server-side API key. Replace example IDs and values before using this request in an approved test environment.

curl --request PUT \
  --url 'https://app.bluenotary.us/api/integrationsv2/sessions/YOUR_SESSION_ID/reschedule' \
  --header "Authorization: Bearer $BLUENOTARY_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
  "session_timing": "2030-01-16T11:30:00-05:00"
}'

Response

200 · Example success Illustrative values in the current response shape.

{
  "response": "Success",
  "response_message": "Session rescheduled successfully"
}

• Validate that the appointment is in the future, the session can be rescheduled, and the notary is available before calling this operation. These checks are not all enforced by the reschedule handler.
• Email notification depends on account configuration; there is no confirmed per-request notification switch here.
• The session_rescheduled event carries updated meeting information. Reconcile event-driven state with Get Session if needed.
• Verify both stored appointment time and actual dispatch behavior across daylight-saving transitions.

Errors & recovery

Explore the response

Keep building