The profile PATCH currently accepts company_name. It does not change the login email, password, tier, wallet or reseller approval. Brand PATCH accepts its documented brand fields, including name, logo reference, colour and support/documentation addresses.

1. GET the current profile or brand. A brand read may return null before any brand is saved.
2. Prepare the intended values. For brand edits, explicitly retain the intended brand_name, primary_color and status, because this helper supplies defaults when those fields are omitted.
3. When the object has a row version, pass the expected numeric version in If-Match. Use the current API contract's supported version format.
4. Submit the PATCH with an idempotency key.
5. Read the saved object again and inspect the relevant customer-facing page or connector publication separately.

This endpoint's helper applies defaults to selected fields even for PATCH. A generic client that assumes every omitted property remains untouched can therefore produce an unintended brand name, colour or draft state. Build the complete intended values for those fields from the fresh read.

No. Saving a brand-domain setting records configuration. DNS, hostname routing and certificate readiness require their own supported setup and verification. Do not publish a new brand address until it is reachable through the intended service.

If a version conflict occurs, reload and compare both edits. Do not remove If-Match merely to force the old payload through. Similarly, use an approved logo asset reference rather than inventing a server filesystem path in the API request.

• Build and publish branded billing-platform connectors in Connector Studio
• Choose Domain Nexus client navigation, themes and translations
• Retry Domain Nexus requests without creating duplicate domain operations
• Get started with the current Nabtech Domain Nexus v2 API