The sugarCRM is hosted on http along with that custom API is expose.
And when we are trying to access the exposed endpoint from different application which is hosted in https.
Does it create a problem ?
The sugarCRM is hosted on http along with that custom API is expose.
And when we are trying to access the exposed endpoint from different application which is hosted in https.
Does it create a problem ?
Hi,
if custom API doesn't work while stock API works well, IMHO it looks like custom API development is not completed yet and has nothing to do with deployment specifics ( http or https) . Make sense?
Best Regards,
Dmytro Chupylka
integroscrm.com
We make work in Sugar CRM system faster, more convenient and efficient
OK, I had completed the custom API as well But still i cant able to deploy. Please go through the below link and help me to resolve the issue.
https://sugarclub.sugarcrm.com/explore/enterprise-professional/f/enterprise-professional-questions/4806/invalid-parameter-custom-endpoint
OK, I had completed the custom API as well But still i cant able to deploy. Please go through the below link and help me to resolve the issue.
https://sugarclub.sugarcrm.com/explore/enterprise-professional/f/enterprise-professional-questions/4806/invalid-parameter-custom-endpoint
Okay, if you are sure the endpoint is developed according to Sugar development practice, I may suggest an option to debug.
I've created a temporary demoinstance sg-examples4.demo.sugarcrm.eu/ (admin/asdf) and you may try to deploy custom API on it then try to call the custom API
It is a standard cloud demo - therefore if the call to custom API fails for it, then the problem is not with the instance or deployments specifics - you should be in a position to focus on API itself or the way you send a request.
Best Regards,
Dmytro Chupylka
integroscrm.com
We make work in Sugar CRM system faster, more convenient and efficient