Patch business customer - update only some values in request
Request
- Base URL: https://api.omnium.no (the document declares no server; this is the origin it was published from)
- URL: https://api.omnium.no/api/BusinessCustomers/PatchBusinessCustomer
- Auth: API key in header Authorization
Request body
Name of company
Tax ID, or other governmental identification number
Customer's credit balance
Customer's credit limit
Customer's remaining credits
Customer's credit is denied if true
Emails for notifications (comma separated)
Phone numbers for notifications (comma separated)
Tags for business customer
Set to 'true' if the business customer has a restricted assortment. This is controlled by prices. If the customer has a customer specific price for a product, the product is automatically included in the customer's assortment. If this is set to 'false', a non-customer specific price will be sufficient for the product to be part of the customer's assortment.
When using puch-out orders, unit conversion lists can be defined in settings. This reflects the corresponding Unit Conversion List for the customer.
When using punch-out domain
Unique ID
Customer identifier - does not have to be unique for each store, etc
Customer phone number
Customer e-mail
Customer url
Customer favorite stores
Customer primary market
Additional customer markets (beyond the primary MarketId)
Customer market group
Preferred customer language code
Customer preferred currency code (E.g. USD, NOK, EUR)
Set to 'false' if you want to update the whole 'properties' list. If true, new properties will be added to the existing list of properties. 'True' by default.
If true, customer is available in all markets / stores
True if customer is inactive, and should not be able to make purchases
Customer's preferred shipping method name (default selected in new carts)
Payment terms (free text)
Net payment terms (days)
Customer details (brief summary for customer service representatives)
Response
Business customer updated successfully
True if at least one property on the customer was changed by the patch operation.
Total number of customers processed by the operation.
Number of customers that were modified and persisted.
Number of customers that were processed but had no changes to apply.
Number of customers that could not be found and were therefore skipped.
Ids of customers that could not be found and were therefore skipped. Null for single-customer operations.
Number of customers where the update failed due to an error.
Concatenated error messages for any customers that failed to update. Each entry includes the customer id and the underlying error.
Changes
No recorded changes to this operation across all 1 revision of this API.