Retries

When a request times out you don’t know whether it reached Sitemark. Requests that carry their own id can be sent again safely.

Send a change id

Every change in Update ticket fields carries its own id, a UUID you generate (UUIDv7 recommended). A change with an id that was already saved is not saved again, so you can resend the whole request after a timeout. Values equal to the current one and DESCRIPTION changes are not saved under their id, so a resend after the value changed applies them and can overwrite the newer value.

Use a new id for every new change: a reused id is treated as the same change. Only resend a request to retry one that failed or timed out; see Update ticket fields.

Rate limits

A 429 response means the request was not processed. Wait for the time in Retry-After, then send the same request again; see Rate limiting.