1. List existing profiles and search for the intended organisation or person before creating a duplicate.
2. POST the required profile_name, first_name, last_name, email, phone_e164, address1, city and country_code.
3. Include the appropriate company, state, postal code and second address line where relevant. Use the current registry requirements for additional fields.
4. Store the returned public contact ID and read the profile back to verify spelling and contactability.
5. Use PATCH with the current If-Match version for later changes. Omitted profile fields are retained by this handler.

It records a local contact state. Setting it in a request does not verify identity, deliver a confirmation message or satisfy a registry's independent contact verification. Keep your administrative evidence accurate and complete the provider's actual required process.

No. Registry-side updates use the domain contacts endpoint for the specific owned domain. Review which contact roles should change and any registry consequences before submitting those operations. A saved billing contact and the legal registrant may represent different people.

Use the supported DELETE workflow after reviewing its references. A profile still used by other records can be protected by relationship constraints. The deletion is not an instruction to erase registry history or change existing registrations.

Keep only accurate data needed for the intended registration tasks, use the correct international phone and two-letter country format, and avoid copying one customer's details into another customer's order merely to pass a validator. A rejected field should be corrected against the real registrant information and current requirements.

• Read stored domain contact assignments through the v2 API
• Update domain contact roles with the current v2 API
• Build domain forms from current registry field and consent requirements
• Keep end-customer registration contacts separate from reseller account ownership
• Create reusable API record sets and preview their stored items
• Resend supported transfer verification and reconcile the resulting state