RVR-PDRIVE-101
- 1 Minute to read
- Print
- DarkLight
- PDF
RVR-PDRIVE-101
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Issue Summary
- The error code
RVR-PDRIVE-101
accompanied by the message "HTTP response status code not OK" indicates a failure in communication between Rivery and the Pipedrive API, likely due to receiving a non-200 HTTP response status code. This suggests that the API request sent from Rivery to Pipedrive might not be configured correctly or the response is not as expected. - Common reasons for such issues include incorrect API credentials, invalid or missing API endpoints, or network connectivity problems.
- The error code
Action Steps:
- Verify API Credentials: Ensure the API key or token being used is correctly set in Rivery and that it hasn't expired or been revoked.
- Check Endpoint Configuration: Confirm that the Pipedrive API endpoint is correctly specified and that any necessary parameters or headers are correctly included in the request.
- Examine API Limits: Make sure you are not exceeding the API rate limits imposed by Pipedrive, which can lead to HTTP error responses.
- Network Issues: Check for any network issues that might be causing connectivity problems between Rivery and the Pipedrive service.
- Test the Connection: Use the "Test Connection" feature within Rivery to check the API connection status. This feature helps verify whether the connection to the API is successful.
- Inspect Logs: Review any available logs for more detailed error messages or stack traces which might indicate the specific problem with the API request.
External References:
- Please refer to the official Rivery documentation for detailed guidance on setting up the Pipedrive connection.
- Review Pipedrive's API documentation to ensure the usage of correct endpoints and authentication methods.
If the issue persists or you need further assistance, please open a ticket with Rivery support.
Was this article helpful?