Thank you very much for all the suggestions and troubleshooting.  After getting the test script to work but mine failing, I concluded that the issue was with my script.  Breaking it down to the bare minimum commands to replicate the functionality in my script AND running it with the splunk binary (rather than just from the command line as the splunk user)  I realized that Splunk was experiencing some problems.  In my original script, I use the curl command but was using the silent flag (-s) so the errors themselves were being hidden from stdout.  Now testing it at its bare minimum, I saw Splunk throwing errors because it was unable to access (or couldn't find for some reason) the SSL CA cert path.  There were 2 solutions to this, either use the -k switch in my curl command, or provide the full path using --cacert.  I tested both and they both work but ended up using solution 2. Testing using the splunk binary /opt/splunk/bin/splunk cmd ./json.sh  Solution 1: (-k) non-ssl cert validation curl -sgk "https://api.website.com/rest_endpoint" -X GET -u "user:api_token" -H 'Accept: application/json'  Solution 2: Provide the path to standard certs curl -sg --cacert /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem "https://api.website.com/rest_endpoint" -X GET -u "user:api_token" -H 'Accept: application/json' ... View more