Sign in
Sending

Reschedule a scheduled send

Changed on

Moves a STILL-SCHEDULED send (status scheduled) to a new execution time. The new scheduled_at must be in the future and at most 30 days out, the same bounds as the create-time field on /send-mail.

The update is a compare-and-swap on status = 'scheduled': once the scheduler has claimed the row for execution, or it was already canceled or executed, the update loses and the call returns a 409 not_scheduled conflict naming the row's current status. A due send can therefore never be moved out from under an in-progress execution.

Returns the full updated sent-email record on success.

patch/sent-emails/{id}

Request

  • Base URL: https://api.primitive.dev/v1
  • URL: https://api.primitive.dev/v1/sent-emails/{id}
  • Auth: HTTP bearer

Path parameters

idstring uuid required

Resource UUID

Request body

scheduled_atstring date-time required

New execution time (ISO 8601). Must be in the future and at most 30 days out, the same bounds as the create-time field on /send-mail. Accepts Z or a numeric UTC offset (2026-10-09T17:00:00Z, 2026-10-09T13:00:00-04:00); an offset is converted to UTC. A time with no zone, or a bare date, is rejected.

Response

Rescheduled sent-email detail

successboolean required

Changes

  • 294207b6de5fRevision changes
    • info

      added the optional property ////// to the response with the status

  • 52138fa51360Revision changes
    • info

      removed the invalid_signup_code enum value from the / response property for the response status

    • info

      removed the invalid_signup_code enum value from the / response property for the response status

    • info

      removed the invalid_signup_code enum value from the / response property for the response status

    • info

      removed the invalid_signup_code enum value from the / response property for the response status