Some things don't just go as planned, eh. Here's how to manage them.
Your integration might experience errors at some point when making requests from MyCover.ai. Here’s how to handle and recover from such errors.
We use the standard HTTPS response codes to indicate the success or failure of all API requests.
2xx codes indicate success.
4xx indicates that an error failed due to the information provided.
Codes in the 5xx range indicate server problems on our end, though less likely to occur.
How to handle errors
Integrations should be able to correct 4xx errors that occur due to the contents of an API request. Where the input is invalid, include a code field to help the integration react correctly.
For errors due to problems arising from Mycover.ai’s servers, we are working to ensure you don’t see them, we promise.
What Errors Mean
400 - Bad Request
Your request was unacceptable because a parameter was missing.
401 - Unauthorized
No valid API key was provided by you.
402 - Request Failed
Your parameters were valid but the request failed.
403 - Forbidden
Your API key doesn't give you the permissions to perform a request.
404 - Not Found
The requested resource doesn't exist.
409 - Conflict
Your request is conflicting with another request.
429 - Too Many Requests
You make too many requests too quickly.
500, 502, 503, 504 - Server Errors
Something went wrong on our end. These are rare though.
200 – Success/OK
Everything works fine, as expected.
If you require assistance with integrations or have any questions, our customer support team is here to help. You can reach out to our support team through email and you can also join our developers' community. We are committed to providing timely and helpful support to ensure a smooth user experience.