Thanks for your time today - just to summarise our conversation this morning your developers will implement the following:
[x] The /api/webUsers API accountLink parameter to be renamed companyName
[x] The /api/webUsers API id parameter will no longer be required just the webUserName, emailAddress
[x] Calling the /api/webUsers API endpoint will return integrationTierUserId
[ ] The integrationTierUserId will be used instead of webUserID when calling api/booking API endpoint
[x] Another API endpoint to be added which the integrationTierUserId will be passed to in order to retrieve a list of companies that the Web User can book as
[ ] All API endpoints to return JSON in cases of an error
[ ] Integration Tier to be served over https
Once these changes have been implemented I will update the website User Registration form to include an optional Company field text field which will be passed to the /api/webUsers API and then amend the website functionality to retrieve a list of companies the Web User can book as from the API.
@PeteHaK @joshgosselin
Thanks for your time today - just to summarise our conversation this morning your developers will implement the following:
/api/webUsersAPIaccountLinkparameter to be renamedcompanyName/api/webUsersAPIidparameter will no longer be required just thewebUserName,emailAddress/api/webUsersAPI endpoint will returnintegrationTierUserIdintegrationTierUserIdwill be used instead ofwebUserIDwhen callingapi/bookingAPI endpointintegrationTierUserIdwill be passed to in order to retrieve a list of companies that the Web User can book ashttpsOnce these changes have been implemented I will update the website User Registration form to include an optional Company field text field which will be passed to the
/api/webUsersAPI and then amend the website functionality to retrieve a list of companies the Web User can book as from the API.