Error codes

your pathfix monitor page will capture all the calls made between your app and the service provider here is a list of errors that you may see and what each of them mean error codes error description insufficient call information either the user id provided is incorrect or the user id and pathfix public key https //docs pathfix com/pathfix private key combination is incorrect consent needed when an api call is attempted to the users provider before the user has consented or token has been revoked api error when the api is not found at the provider end occurs when the provider returns an error eg \ when there is error in the api payload \ when the error has been discontinued by the provider \ when api attempted is not within the scopes authorized ip blocked error that is raised by the firewall when any of the configured firewall rules for ip or javascript origins https //docs pathfix com/javascript origins firewall do not match please check the firewall settings this could also be due to an incorrect private key https //docs pathfix com/pathfix keys added while making the call, check the instructions section of your application in pathfix and make sure you have added the private key and public key to your call unknown error this represents a handled error and is notified internally to the team if you believe you should not be getting this error, please email us at support\@pathfix com https //mailto\ support\@pathfix com with your external ip as displayed at whatismyip com https //whatismyip com and we will get back with a resolution unauthorized domain the originating domain has not been updated in your pathfix application log in to your pathfix account, click on edit under your application and add your app domain under the 'application domains' section pathfix will handle all token and payload delivery related errors and guarantees an annual uptime percentage of 99 5% blocked duration for api, rpm and invalid oauth id errors when an account encounters a high number of errors there is a risk of the api provider blacklisting the servers of origin (pathfix) to prevent this, pathfix automatically blocks apps with several repetitions of this behavior the blocking duration is marked by the email that is sent out by pathfix below is the block duration based on the number of instances instance block duration first 1 hour second 6 hours third 12 hours fourth 24 hours fifth+ 24 hours x (instance count 3) e g for 6th instance 24 (6 3) = 72hrs to workaround the rpm quota errors, you can upgrade to a custom plan but the behavior with the api and invalid oauth id errors will follow the above block duration need help? reach out to us at support\@pathfix com and we would be happy to assist!