All the endpoints that can be called on the Customer controller.
Endpoints that require the CUSTOMER_READ permission:
GET index
GET item
POST searchByPrimaryExternalId
GET timelineByCustomerExternalID
Endpoints that require the CUSTOMER_CUD permission:
POST index
PUT index
PUT item
DELETE item
POST addChannelOnly
PUT updateCustomer
DELETE itemChannel
DELETE itemPurgeData
POST externalEvent
POST syncWithCRM
POST createCustomerCRUD
Returns the timeline from this customer by external primary ID.
External primary ID of the customer.
Include this with any value to also return ticket history for the customer.
No content
Creates a new customer.
Most parameters are optional but depending on the presence of other parameters.
Name or the ID of the channel e.g. email or telephone.
Can only be processed if customer_link_channel is set.
^([0-9]+|email|telephone|facebook|twitter)$The name of the address, depending on the channel e.g. a phone number or an email address.
If enable customer search by channels is enabled on the brand, this can be used instead of primary_id
The external primary ID of the customer.
Not needed if enable customer search by channels is enabled on this brand. This will take precedent if it is included.
Does not update the ticket with the new linked channel(s) if sent along with the request.
""Pattern: ^[a-zA-ZÀ-ÖØ-Þß-öø-ÿŠš\.\-\' ]+$""Pattern: ^[a-zA-ZÀ-ÖØ-Þß-öø-ÿŠš\.\-\' ]+$Allows for instant linking the new customer to a ticket.
^\+[0-9]+$No content
Updates this customer's name.
PrimaryID, brandID and customerID are all optional, but dependent on the presence of at least one.
""Pattern: ^[a-zA-ZÀ-ÖØ-Þß-öø-ÿŠš\.\-\' ]+$""Pattern: ^[a-zA-ZÀ-ÖØ-Þß-öø-ÿŠš\.\-\' ]+$No content
Updates any fields existing on this customer, including custom fields.
See the example for how to update custom fields. It should always follow the pattern of custom_ followed by the name of the custom field.
If you want to update or add multiple customer channels at once, it should be done in 2 parameters:
customerChannelType_0 (corresponding to the channel type ID)
customerChannelValue_0 (corresponding to the address of the channel you want to add)
The 0 would be incremental if you choose to do multiple.
""Pattern: ^[a-zA-ZÀ-ÖØ-Þß-öø-ÿŠš\.\-\' ]+$""Pattern: ^[a-zA-ZÀ-ÖØ-Þß-öø-ÿŠš\.\-\' ]+$This is a custom customer field. Any custom fields you want to update start with custom_ followed by the name of the custom field.
This is how you would add/update multiple customer channels at once. the 0 would be incremental if you add/update multiple. This should always be the channel type.
This is how you add the value to the customer channel you want to add. The same goes for how the customerChannelType gets added, only this would be the value.
Successful example
Adds a channel to a customer.
^\+[0-9]+$^[a-zA-Z0-9_ ]+$No content
Updates the fields of this customer.
Similar to how PUT item works.
If you want to update custom fields, just put the name of the field you want to update as the key and the value of the field you want to update as the value.
^[a-zA-ZÀ-ÖØ-Þß-öø-ÿŠš\.\-\' ]+$^[a-zA-ZÀ-ÖØ-Þß-öø-ÿŠš\.\-\' ]+$This is a custom customer field. Any custom fields you want to update start with custom_ followed by the name of the custom field.
This is how you would add/update multiple customer channels at once. the 0 would be incremental if you add/update multiple. This should always be the channel type.
This is how you add the value to the customer channel you want to add. The same goes for how the customerChannelType gets added, only this would be the value.
No content
Creates a new customer event e.g. an order or marketing mail to the customer timeline.
The external primary ID of the customer.
No content
Creates a customer using the CRUD.
The external primary ID of the customer.
^[a-zA-ZÀ-ÖØ-Þß-öø-ÿŠš\.\-\'' ]+$^[a-zA-ZÀ-ÖØ-Þß-öø-ÿŠš\.\-\'' ]+$This is a custom customer field. Any custom fields you want to update start with custom_ followed by the name of the custom field.
This is how you would add/update multiple customer channels at once. the 0 would be incremental if you add/update multiple. This should always be the channel type.
This is how you add the value to the customer channel you want to add. The same goes for how the customerChannelType gets added, only this would be the value.
No content