...

• <reason>: will be an identifier that will try to narrow down the type of error. Will show ‘UNKNOWN’ if the error type isn’t known. Current examples are: ‘VALIDATION’, ‘DATABASE’
• <errorUUID>: This is a regular old UUID which you can pass on to InTouch support which will simply let us have an easy way to find the error in the Connector logs
• <message>: the actual details of the error. Note that currently this is just the stack trace from the real error in the backend so some errors might be cryptic

Appendix

Always returning the InTouch UUID in a GET call

In order to send referral leads through the web lead form service, the InTouch user UUID of the person who referred the new lead is required. This page outlines the web service call to GET an InTouch member UUID for an existing record.

<user>
   <providerInfo>
      <identifier>PROVIDER_ID</identifier>
      <clientID>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</clientID>
      <clubID>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</clubID>
      <recordID>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</recordID>
   </providerInfo>
   <extraProviderIDs>
       <inTouchID>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</inTouchID>
    </extraProviderIDs>
   <userInfo>
      <firstname>Foo</firstname>
      <lastname>Bar</lastname>
      ...
   </userInfo>
</user>