Resend a communication

POST /api/communications/schedule-job/resend-communication/{communicationHistoryId}

Overview

Sends one already-sent communication again, exactly as it went out the first time.

Nothing is rebuilt. The stored sender address, recipient address, subject and HTML body are read from the communication history record and handed straight to the email provider, with a plain-text alternative derived from the stored HTML. Placeholders are not re-evaluated, so the copy repeats the data as it stood when the original was generated, and it goes to the address recorded at that time rather than to the member's current address. Correcting a member's email address first will not change where the resend lands.

Delivery is always by email, whatever channel the original communication used. A 204 No Content means the message was accepted by the email provider, not that it reached the recipient. There is no de-duplication: each call sends another copy.

Endpoint

POST {base_url}/api/communications/schedule-job/resend-communication/{communicationHistoryId}

{base_url} is the environment URL issued to your integration. See Authenticating with Gladstone APIs.

Path parameters

NameTypeRequiredDescription
communicationHistoryIdinteger (int32)YesThe communication history record to send again — one entry in the log of individual messages sent, not the id of the job that sent them. Must be 1 or greater.

Sample request

cURL
curl -X POST '{base_url}/api/communications/schedule-job/resend-communication/{communicationHistoryId}' \
  -H 'Authorization: Bearer {accessToken}' \
  -H 'X-Use-SSO: true'

Errors

StatusMeaningWhen
400Bad requestcommunicationHistoryId is zero or negative (Id must be a valid number), or the path segment is not an integer.
404Not foundNo communication history record with that id in this tenant (Communication for id {id} does not exist.).
500Internal server errorThe history record has no member associated with it — a member is optional on a history record but required to resend — or the email provider rejected the message. Provider rate limiting also surfaces here as a 500 rather than a 429. The response has no body.

This page as markdown · All pages · llms.txt