The access token received from the authorization server in the OAuth 2.0 flow.
This is the name of your application, e.g. "MyApp/1.0.0". It is used to identify your application.
This is where the version number of your application is entered, e.g. "1.0.0".
The User-Id (int or uuid) on whose behalf the request is executed. Requires scope 'Application.RunAs'.
The id of a session in which the call will be executed.
The Company-Id (int or uuid) of the company on whose behalf the request is executed.
The tenant ID for the target ERP instance.
Request parameters
Updates a customer - Request
Id of the customer.
"b45f6432-2462-4c6f-b00f-1d9d01000000"
Id of the company the customer belongs to. Optional — if omitted, the existing company assignment is left unchanged.
"b45f6432-2462-4c6f-b00f-1d9d01000000"
Customer group for the customer to be in.
"b45f6432-2462-4c6f-b00f-1d9d01000000"
The customers category ID.
"b45f6432-2462-4c6f-b00f-1d9d01000000"
The customers preferred payment method ID.
"b45f6432-2462-4c6f-b00f-1d9d01000000"
The accounts receivable number of the customer.
The customer's date of birth.
The customer's commercial register number.
Number of the customer. If no number is given when posting a customer, the number will be generated automatically.
The customers ebay name.
The customers homepage URL.
The source of initial contact. This could be for example a specific sales channel, a convention or a marketing campaign.
States if a customer is from a cash-register or point of sale and if their data should be synchronized with JTL-POS, for example.
The customer's locked status.
The customer's preferred language in ISO format (e.g. "de", "en").
The customer's tax identification number.
Addresses of the customer.
Settings relevant to payment for the customer.
The date and time of the customer's creation.
Customer changed successfully