Customers

a ' customer ' in tamio denotes an individual who has engaged with your business through various touchpoints such as checkout, form captures, etc , or who has been manually added via the dashboard or api each customer supports multiple billing details, shipping information, business classification and vat number validation tamio enables you to employ customers feature in diverse ways, including but not limited to generating direct one off invoices scheduling recurring invoices managing store vouchers dispatching direct emails organizing newsletter campaigns monitoring performance tracking generating reports developing sales conversion flows collecting product reviews utilizing automations api handling ticketing conducting sms campaigns creating custom checkout flows with the transactions api implementing sales representative processes (e g , assigning customers to teammates, tracking team conversion performance) managing crm & lists personal information & gdpr each customer has a corresponding customer object docid\ x0e6zfnwaym4bwj4a82ex with essential personal details like address, city, business classification and preferred language your customers' personal information is stored in servers in germany, thus being fully gdpr compliant according to eu legislation customers are classified by their category, which can be customer or lead leads are a unique type of customer that you can learn more about leads docid\ gspqux7tg931elqq06dh6 api endpoints description method url create customer docid\ cuemhngxn3hftqavvmmtb post post /v2/customers/create retrieve customer docid\ xewvukzzgye whpwxxdaw get get /v2/customers/retrieve/\ id update customer docid\ k 6gnpnhd8usraxppvwch post post /v2/customers/update/\ id add to list docid\ e3yle8ausodgvmad4cslp post post /v2/customers/add to list/\ id remove from list docid\ mglve8jhtevernjrmgsag post post /v2/customers/remove from list/\ id delete customer docid\ vzcfasmuugpljrtuaisu8 delete delete /v2/customers/\ id bulk delete docid\ y rl95tqzlr7tobmfuyzt post post /v2/customers/bulk/remove send email docid\ xxtqsr1w54rvudq sbfcj post post /v2/customers/send email/\ id bulk send email docid\ owup4xo2qxjs17hx21ikc post post /v2/customers/bulk/send email bulk add to mailing list docid\ uoa9e qaj4fflqyexyrrb post post /v2/customers/bulk/add to list bulk create docid\ nov razg9v4rq5crpdj5f post post /v2/customers/bulk/create bulk assign to teammate docid 9jvmx0zol7nvre4njpjtm post post /v2/customers/bulk/assign to teammate list all customers docid\ b3e1szzsbay8xiowr5xje get get /v2/customers/list webhook events there are three webhook notification events associated with the customers api customer created customer updated customer removed you can see examples of notification events customer events docid\ vpxf3upxl n7gflcvvism permissions whether managing teammates or creating api developer keys, you can customise permissions when accessing customers api resources the default set of permissions are view , edit , create and remove moreover, permissions can be extended down to an individual customer level, meaning that you can provide access to specific customers on your account