...

• <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

...

Turnup

This section details what is necessary to get a new client turned-up on the Connector.  The turn-up process for your system may vary slightly from other systems if there are any custom configuration options.

Information required

• The client ID number in your system
• The club ID numbers in your system (1 for every club)
• Connection information (not required for full SaaS platforms)
  
  • IP
  • Username/Password
  • Scheme (http/s)
• Any custom configuration options built into the Connector for your platform

Security

Security will be built into phase 2 of the Connector.  Each system making calls to the Connector will require a username & password.  It is yet to be determined if per client (or per club) access will be required (i.e. club must sign waiver to gain access)