Error code brand_transfer_ended (HTTP 409)
What Synq's `brand_transfer_ended` error code means, when the API answers HTTP 409 Conflict with it, and how to fix it.
The brand move ended before this decision: reason is its status, accepted, declined, cancelled or expired.
What to do
Read the request again for its status; ask for a new move if the brand should still go.
| Field | Value |
|---|---|
code | brand_transfer_ended |
status | 409 Conflict |
title | Brand transfer ended |
Synq's APIs answer errors with a problem document (RFC 9457, application/problem+json). Its type is the address of this page, and its code is brand_transfer_ended. Branch on code, never on title or detail: a code never changes once it ships, while the words may.
{
"type": "…/errors/brand_transfer_ended",
"title": "Brand transfer ended",
"status": 409,
"code": "brand_transfer_ended"
}See every error code. Still stuck? Support says where to write, what to send and where Synq's status page is.
Error code transfer_target_unavailable (HTTP 422)
What Synq's `transfer_target_unavailable` error code means, when the API answers HTTP 422 Unprocessable Content with it, and how to fix it.
Error code transfer_preview_changed (HTTP 409)
What Synq's `transfer_preview_changed` error code means, when the API answers HTTP 409 Conflict with it, and how to fix it.