Update customer
Update a customer and add, change, or delete its locations. Identify the customer by resourceId, as returned by Create customer or List customers.
Usage notes:
- Customer fields you leave out keep their values. Send an empty string to clear
scacorediId. locationslists only the locations to add, change, or delete; locations you leave out are not changed. A location with aresourceIdis changed, or deleted withrequestAction: "delete". A location without aresourceIdis added; set itscustomerIdto the customer’sresourceId.- When you change a location, send all of it, including
isDefaultand itsaddress(with the addressresourceIdto change that address in place). Location fields you leave out are reset or cleared; see thelocationsschema. A changed location without anaddressis rejected with a 500 error. - List customers returns only part of a customer: not
ediId,isTaxExempt, or a location’sisDefault,usedForBilling,externalLocationId, contact details or address. Keep the full record that Create customer and Update customer return, including addressresourceIds, and treat your system as the source of truth for those fields. An address sent without aresourceIdreplaces the location’s address. - At most one location is the default. To move the default, list the current default with
isDefault: falsebefore the new default. - Renaming the customer or a location also updates clear references to the old name in revenue agreements, invoice settings, and workflows: the same updates the ARMS customer form makes without asking. Ambiguous references are left unchanged.
- Renaming the customer also renames its
<name> Adminand<name> Operatoruser groups, acting as the user inx-arms-assume-user. If that user cannot update user groups, the rename can fail; rename the customer in ARMS instead. - There is no upsert: updating a customer ID that does not exist returns 404.
- A missing permission returns 401.
Authorizations
Your ARMS API key
Email of a user assigned to the appropriate user group
Query Parameters
Carrier identifier; required for all endpoints
Body
Customer fields you leave out (or send as null) keep their current values.
ID of the customer to update, as returned by Create customer or List customers.
New customer name. Cannot contain /. Renaming also renames the customer's <name> Admin and <name> Operator user groups.
Must be a SCAC Cedar already knows. Send an empty string to clear it.
Must be unique across every customer in Cedar. Send an empty string to clear it.
Only the locations to add, change or delete. Locations you leave out are not changed.