Troubleshoot the CRD REST API

Check connection, authentication, request formatting, and execution in that order. Keep the timestamp, request, response, and any ExecutionId available while you investigate.

The API Service cannot be reached

Open Options > REST API in CRD and confirm that the API Service is installed and running. Check the configured protocol, server name, and port. Test the Ping endpoint from the CRD server, then from the integration host. If local access works but remote access fails, check name resolution, routing, and firewall access.

Authentication is rejected

Check that your authentication flow uses the correct token endpoint and valid credentials. For client credentials, check the API client configuration. Send the access token in the authorization format required by that flow, and request a fresh token if the existing one has expired. See Authentication and Token Management.

A request is rejected or returns an unexpected response

Compare the HTTP method, route, headers, field names, and value types with the API Reference. Follow the content type and schema documented for that endpoint, and review the response body for error details.

A schedule does not finish or its output is missing

Confirm that the CRD Scheduler is running and that the schedule ID and type identify the intended schedule. Check its report, parameters, and destinations. For asynchronous runs, use the returned ExecutionId to check the existing execution before submitting again. Review the final result and verify the destination separately.

Contact Support

Include the endpoint, timestamp, CRD version, sanitized request and response, and execution ID if available. Remove passwords, Client Secrets, access tokens, and confidential report content before sharing diagnostics.