Update a customer contact (PATCH)
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/customer-contacts/v1-customer-contact-update-patch.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
PATCH/
Changes the fields you send and returns the contact. is_primary is not changed here: use Set the primary contact.
Use PUT: it checks the fields. PATCH takes the same body but checks nothing.
A contact can give someone access to the Customer Portal (a portal account with the contact's email). Changing that contact's email moves the access: portal_email_scope says whether the account's sign-in email changes on every customer it can open (all_customers) or only this customer's access moves (this_customer), and portal_reconnect_confirmed: true confirms moving it to an account that already uses the new email.
Business rules
is_externalandexternal_typeare ignored: sending them (for example a value you read back) is not refused and changes nothing. Only the Shopify sync sets them.- Customers synced from Shopify are read-only here: changes are refused with 422
validation_error"External customers are read-only. Manage changes from Shopify." System customers (is_system: true) are refused the same way ("System customer cannot be modified or deleted."). - Contacts synced from Shopify are read-only (422).
- On a live customer (not a system or Shopify customer) a contact's email is saved trimmed and in lower case, and two live contacts of the customer can't have the same email (compared the same way). Other customers may use the same email.
- Changing the email of a contact that gives someone Customer Portal access moves that access with it: see
portal_email_scopeandportal_reconnect_confirmed. Sendingemail: ""clears the email and removes the contact's portal access for this customer. PUTchecks thatportal_email_scopeisall_customersorthis_customerand thatportal_reconnect_confirmedis a boolean;PATCHdoesn't.- To clear a text field, send an empty string;
nullis ignored (it is dropped before the request is read).
Side effects
- Sends the
customer_contact.updatedwebhook. - Portal access moves with a changed email. With
all_customersand no other account on the new email, the account's sign-in email changes, its password is cleared, its signed-in sessions end, its contacts on other customers get the same email (without webhooks), and the old address is emailed that the sign-in email changed. Otherwise the access (only this customer's withthis_customer) moves to the account that uses the new email, which is created, invited, when there is none. - When the contact's email already belongs to a Customer Portal account on your team that can't open this customer yet, saving the contact gives that account access to this customer (active when the account is set up with a verified email or a password, invited otherwise). No email is sent.
Path parameters
Your team slug, shown as Team ID next to your API key in Profile.
- Example
your-team
- Example
The customer's id (
idfrom List customers or Create a customer). A hash id from an earlier answer; unique keys and document numbers (such asPO0042) don't work here.- Example
EDhVUaC6jbLbed
- Example
The contact's id (
idfrom List a customer's contacts, or from List a vendor's contacts). A hash id from an earlier answer; unique keys and document numbers (such asPO0042) don't work here.- Example
uAu3dAKIaHyAYk
- Example
Request body
application/json, required.
default_receive_smsbooleanemailstring (email)Saved trimmed and in lower case.
""clears it.faxstringChecked as a real number for
fax_country.fax_countrystringfirst_namestringThe contact's first name.
last_namestringThe contact's last name.
phonestringSend
phone_countrywith it.phone_countrystringTwo-letter country code of
phone, such asUS. Required withphone.portal_email_scopestringRead only when you change the email of a contact that gives someone Customer Portal access.
all_customers(the default) changes that portal account's sign-in email, and the email of its contacts on every customer it can open.this_customermoves only this customer's access to the account for the new email. Required when the account can open more than one customer.- One of:
"all_customers","this_customer"
- One of:
portal_reconnect_confirmedbooleanSend
trueto confirm moving this contact's Customer Portal access to the account that already uses the new email. Defaults to false.send_invoicebooleanStored with the contact and returned as
send_invoice.
More examples (1)
Change the email of a contact with Customer Portal access, on every customer
curl -X PATCH 'https://secure.yoprint.com/v1/api/store/your-team/customer/EDhVUaC6jbLbed/contact/uAu3dAKIaHyAYk' \ -H 'Authorization: Bearer YOUR_API_KEY' \ -H 'Accept: application/json' \ -H 'X-Yoprint-Decimal-Format: exact-v1' \ -H 'Content-Type: application/json' \ -d '{ "email": "alex@example.com", "portal_email_scope": "all_customers" }'Response
200Successful response.
Child fields (18)
True when the contact is deleted.
customer_idstringCustomer contacts only.
default_receive_smsbooleanemailstring | nullexternal_typestring | nullfaxstring | nullfax_countrystring | nullis_externalbooleanTrue for a contact synced from Shopify; such contacts are read-only.
last_namestring | nullphonestring | nullphone_countrystring | nullsend_invoicebooleanCustomer contacts only.
vendor_idstringVendor contacts only.
Errors
401The API key is missing or wrong (
unauthenticated).403You are not allowed to do this.
api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only{"message": "Insufficient Permission"}. Other refusals use the error envelope, withunauthorizedoruser_is_not_authorized.- When
- The change moves portal access on a customer your role can't update: you need Manage Customers "Manage All", or "Manage Assigned to User" and to be assigned to every customer the change covers. This 403 has a short body,
{"message": "You need permission to update every linked customer."}. - Fix
- Ask a member who can update those customers, or send
portal_email_scope: this_customer. - When
- Your role has no Manage Customers permission. This 403 has a short body,
{"message": "Insufficient Permission"}, with nosuccessorerror. - Fix
- Ask a team owner to give your role Manage Customers.
404Not found.
page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's.code: null, with a message that starts "No query results for": there is no record with that id.- When
- The contact is deleted, or belongs to another customer.
error.codeis null anderror.messagenames the record type. - Fix
- Restore it first, or check the ids.
409
- When
- Another live contact of this customer already has this email, ignoring case and surrounding spaces (
error.codecustomer_portal_duplicate_contact_email, "This customer already has a contact with that email. Edit the existing contact or use a different email."). - Fix
- Update the existing contact instead, or use another email.
- When
- The contact gives Customer Portal access to an account that can open several customers, and
portal_email_scopewas not sent (error.codecustomer_portal_email_scope_required). - Fix
- Send
portal_email_scope:all_customersorthis_customer. - When
- The new email already belongs to another Customer Portal account and
portal_reconnect_confirmedis nottrue(customer_portal_email_reconnect_required), or that account is disabled or deleted (customer_portal_account_unavailable), or it already has another contact on this customer (customer_portal_duplicate_contact_email). - Fix
- Send
portal_reconnect_confirmed: trueto move the access to that account, or use another email.
422The request was refused and changed nothing.
validation_failedlists what to fix inerror.fields; other codes name a business rule, explained inerror.message. A few checks answer with only{"message": "..."}. An operation that calls another service (a payment provider, a carrier, an accounting app) can answerconnect_timeout("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.- When
- A phone or fax is not valid for its country, a field has the wrong type, or
portal_email_scopeis notall_customersorthis_customer.error.codeisvalidation_failed. - Fix
- Send the country code with the number.
- When
- On a live customer, the email is longer than 191 characters or is not a valid address (
error.codecustomer_portal_email_invalid, "Enter a valid email address using supported characters."). - Fix
- Send a valid email of at most 191 characters.
- When
- The customer comes from Shopify, or is a system customer (
error.codevalidation_error, with the reason inerror.message). - Fix
- Change Shopify customers in Shopify. System customers cannot be changed.
Related
- PATCHSet the primary contact
/v1/ api/ store/ {team_slug}/ customer/ {hash_id}/ contact/ {id}/ primary - PATCHUpdate a contact by id (PATCH)
/v1/ api/ store/ {team_slug}/ contact/ {id}
