Customer Event
The customer event fires every time a customer record is created or updated in myKaarma. The payload mirrors the response from the myKaarma Customer API. Full field documentation for customerWithVehicles is also available here.
The customer object in this payload will include four read-only attribution fields, each a string or null — creatorUserUuid, updaterUserUuid, creatorServiceSubscriberUuid and updaterServiceSubscriberUuid — identifying the user and API consumer that created and last updated the customer.
The createdBy and updatedBy fields will be enhanced to provide more granular source information and may then contain one of the following values:
KCUSTOMER_API, KAARMA_SERVICES, API_INTERNAL, API_EXTERNAL, DMS, DMS_CUSTOMER_PULL,
DMS_RO_PULL, DMS_FI_PULL, DMS_PARTS_PULL, DMS_APPOINTMENT_PULL, DMS_VEHICLE_PULL,
DMS_CUSTOMER_PUSH, OTHER
These values will also be returned for customers created or updated before this date.
What you need to change
- Make the required changes on your side to consume the four new fields if needed, or ensure your consumer supports unknown fields.
- Make the required changes to support the new possible values of
createdByandupdatedBy, or ensure your consumer supports unknown values.
Important Notes
- Customer events are pushed via an indexer job that runs once per second.
- If a customer is updated multiple times within one second, you will receive a single event with the final state.
Field Reference
payloadTop-level payload for the customer event.
In the actual webhook delivery, payload is a stringified JSON string (not an object). The example above shows it as a parsed object for readability.
How to Test a Customer Event
Login to https://app.mykaarma.com using the user credentials provided to you.
In the Customer tab, click on NEW button:

Fill in the fields in the Add Customer Dialog and click Save. You should receive an event on your webhook URL for this customer creation:

In the Customer tab, search for and select the customer you want to edit:

Click on the EDIT button:

Fill in/update the fields in the Edit Customer Dialog and click Save. You should receive an event on your webhook URL for this customer update:

FAQ
Are customer events 1:1 in terms of customer updates?
Not always, the indexer job runs once per second, so multiple updates within one second produce a single event with the final state.