Omoto CRM API

introduction the crm api offers a standard way to push crm data from any third party crm or customer platform into omoto omoto consumes the customer data sent in each trigger and, after performing basic validation and executing business rules, sends out the relevant survey invite to the customer we appreciate that every crm would have their own api structure, and therefore this document standardises the json structure in which omoto can consume data from any third party crm api definition the api is made available on a custom end point that follows the below structure the customer contact and qualifying information is sent as json payload in the body of the post request the json structure is also shared below json payload to be sent in the post request body sample json \[ { "personalinfo" { "firstname" "bertram", "lastname" "wooster", "email" "bertie\@jeeves com", "mobileno" "9835132376" "transactionid" "202005201623", "regid" "tst202005201144" }, "qualifyinginfo" \[ { "name" "unitname", "value" "book club" }, { "name" "genre", "value" "comedy" }, { "name" "author", "value" "pg wodehouse" }, { "name" "publisher", "value" "jenkins" }, { "name" "country", "value" "uk" } ] } ] important notes 1 set content type to 'application/json' 2\ api keys are used for both authentication and campaign identification make sure you use the right api key for the right campaign 3\ omoto sends out the survey invite immediately after receiving the trigger scheduling and timing must be managed your end trigger when invite has to be sent