https://community.appian.com/discussions/f/integrations/22663/api-path-segment-issueHi All, i am using path segments to extract data from the request and i&#39;m testing the API through postman everything worked fine in dev environment but when it goes to the higher environment its not working for example abc/bcd/cde http!request.pathsegmentsen-USTelligent Community 12https://community.appian.com/thread/88656?ContentTypeID=1Fri, 03 Dec 2021 14:11:27 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:f125d895-cf7f-4096-b0e4-2ac94873663bPeter Lewis<p>Hmm, I&#39;m not sure then - it does seem kind of strange, but maybe Postman is adding an extra path segment somewhere? Can you see in Postman the exact request that is being made (and does it match what you&#39;re using in Appian)?</p><div style="clear:both;"></div>https://community.appian.com/thread/88621?ContentTypeID=1Fri, 03 Dec 2021 06:32:22 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:942319c3-15aa-40ec-b4b9-e0e2db8584ccudhay kumar<p>Yes peter i have tried to return the pathsegments as a response its returning same in all 3 environments and in all environments its working fine if i test the api from appian. But when i test through postman 3rd environment is not working </p><div style="clear:both;"></div>https://community.appian.com/thread/88613?ContentTypeID=1Thu, 02 Dec 2021 22:38:58 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:debc256c-bbdc-4c0a-8e55-610de6145a57Peter Lewis<p>What happens when you just return all the path segments as a list in your response? Does it show something else in the response in dev vs higher environments? What other steps have you tried so far to troubleshoot this?</p><div style="clear:both;"></div>