Update a business customer
input only the fields you need to update.
Request
- Base URL(relative, and it does not resolve against the document’s source URL)
- Auth
- API key in header sessionKey
- or API key in header clientCode
- or API key in header jwt
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
customer Id
Query parameters
if the flag is present, then the previous card number value gets saved as an old card number
Request body
Global Location Number.
Number of customer's bank account.
IBAN number of customer's bank account.
Name of customer's bank.
BIC/SWIFT identifier of customer's bank account.
area of business.
Registry code
Color that the customer entry is marked with. Possible values: "", "yellow", "red", "blue", "green".
Customer’s country.
Customer’s credit limit: the maximum amount of money (in account default currency) that they are allowed to owe.
Flag indicating that Erply does not keep track of the customer's balance (amount prepaid or due)
Customer manager (must be an employee
Default payment deadline (in days).
A field that propagates from customer records to sales documents and lets the company categorize shipments by delivery method or delivery time.
Whether the customer is marked with a do not sell flag or not.
In UI, the field is titled “E-invoice email address”.
Customer reference for e-invoices.
0 or 1: whether the customer wants to receive invoices via electronic channels.
E-invoice integration parameter.
EDI type. Possible values: 2DOC, 4DOC, SPECIAL.
Flag indicating that this customer does not want to receive email correspondence.
Employee ID of the employee changing this company customer.
Factoring contract number.
Gender. Erply API only accepts "male" "female" or an empty string.
Additional, custom home store ID
Location where the customer shops most frequently. https://learn-api.erply.com/requests/getwarehouses
Corresponding customer identifier in a system integrated with Erply (e.g. accounting software)
0 or 1: whether the customer wants to receive invoices via docura.
0 or 1: whether the customer wants to receive invoices via email.
Mark if a customer should be starred
Assign the code of customer's loyalty/membership card. This code must match the sequence produced by card swipe.
Name.
E-invoice integration parameter.
0 or 1: whether the customer wants the e-invoice operator to deliver paper mails (if such option is supported).
“Payer of invoices” (another customer).
Flag indicating that this customer pays via factoring (all invoices must be addressed to a designated third party)
Late fee / penalty for overdue invoices. The semantic meaning of this value is not strictly defined; usually we expect it to be “% per day”
Peppol ID
Flag indicating that coupons must not be automatically printed to this customer.
Assign the customer a price list
ID of the primary store
Customer’s reference number for sales invoices. Assign a reference number - if system is configured to use hand-created customer reference numbers. By default, not necessary, since reference numbers are created automatically.
Flag indicating that the customer will not earn points for purchases. (They can still spend existing points though.)
Flag “Sales for cash only”. By default, false
ID of the secondary store
A flag indicating that this customer wants to get goods with Waybills, not Invoice-Waybills.
Location where the customer signed up. https://learn-api.erply.com/requests/getwarehouses
Flag indicating that this customer must not be charged sales tax.
Feature used by Greek customers: office where the customer / supplier reports to. (This value must be shown on some printouts.)
Customer type. Possible values are "DOMESTIC", "EU", "OUTSIDE_EU".
Customer's VAT number.
This is for web shop integrations: to store customers' web-shop login credentials in Erply.
Response
OK
Example response
{
"id": 73
}Changes
No recorded changes to this operation across all 1 revision of this API.