Retrieve your customer database.
In addition to customer card fields, you can have API to return:
getCustomers
call, you are responsible for logging everything you do with the data. If it is not possible to keep the logs in the system that processes the data, you may consider writing the log entries into Erply, with the logProcessingOfCustomerData call.
This call is deprecated. For managing customer addresses, use CRM API.
The corresponding new call is: GET /v1/addresses.
Retrieve customer, supplier, or company addresses.
Important: if you operate in the European Union, the General Data Protection Regulation (GDPR) requires all processing done with customers' personal information to be logged. If you retrieve customer addresses, you are responsible for logging everything you do with the data. If it is not possible to keep the logs in the system that processes the data, you may consider writing the log entries into Erply, with the logProcessingOfCustomerData call.
This call is deprecated. We recommend to use CRM API instead.
The corresponding new call is: GET /v1/customers/groups or GET /v1/customers/groups/indented (for populating a dropdown list).
Get customer groups. In Erply, customer groups are hierarchical; a group can contain sub-groups.
This call is deprecated. For managing customer addresses, use CRM API.
The corresponding new call is: GET /v1/addresses/types.
Retrieve address types.
Get the ID of default customer used for POS transactions (typically, "POS Customer", "Walk-in" or similar).
If such a customer is not defined, API returns no records.
This call is deprecated. We recommend to use CRM API instead.
Create a new customer or update customer information. Function can be used for manipulating both companies and persons. Some parameters only apply to one or another.
If the created or updated customer is a natural person and your account country is subject to the General Data Protection Regulation (GDPR), Erply logs the change in the customer information processing log.
Create or update customer's or supplier's address.
If the created or updated address belongs to a customer (to a natural person), and your account country is subject to the General Data Protection Regulation (GDPR), Erply logs the change in the customer information processing log.
This call is deprecated. We recommend to use CRM API instead.
The corresponding new call is: POST /v1/customers/groups.
Create or update a customer group.
Validate customer's web shop user name and password.
This API call is for building a web shop that has a log-in (members-only) area. In Erply Customer module, you can assign a user name and password for each of your customers. (These user names / passwords DO NOT grant the customer any access into your Erply account, and cannot be used for that purpose. They can only be used in your web shop.)
Use API verifyCustomerUser
to validate the user name and password and retrieve the customer record that these credentials belong to. Calling This API call will not create any "session" or make the customer somehow logged into API; it just serves a verification purpose.
Instead, if you want to learn how to generally authenticate yourself when connecting to Erply API — to be able to issue any API calls at all — see verifyUser.
This call is deprecated. We recommend to use CRM API instead.
The corresponding new call is: DELETE /v1/customers/businesses/{ids}, DELETE /v1/customers/individuals/{ids}.
Delete a customer.
If the deleted customer is a natural person and your account country is subject to the General Data Protection Regulation (GDPR), Erply logs the deletion in the customer information processing log.
This call is deprecated. For managing customer addresses, use CRM API.
The corresponding new call is: DELETE /v1/addresses/{ids}.
Delete a supplier / customer / company address.
If the deleted address belongs to a customer (to a natural person) and your account country is subject to the General Data Protection Regulation (GDPR), Erply logs the deletion in the customer information processing log.