Update Dropship Branding
PUT/api/portal/dropship/branding
Updates the packing-slip branding. Only the fields sent are changed; omit a field to keep it. Orders already placed keep the branding they were placed with.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Body (every field optional)
display_name(string or null, max 255) — may not be blank when sent.support_email(email or null, max 255).support_phone(string or null, max 64).slip_message(string or null, max 2000).return_address(object or null; null clears it). When sent:name,address1,cityandcountry_code(2-letter ISO) are required;company,address2,address3,province,province_code(max 16),zip(max 32),country,phone(max 64) andemailare optional (strings, max 255 unless noted).
The logo is uploaded separately with Upload Dropship Logo.
Returns 422 for invalid fields. Returns 403 with code: dropship_branding_not_allowed and a message saying why when the buyer is not a company admin, dropship is not turned on for the account, or the merchant manages the branding itself. Viewers get 403 viewer_read_only.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.