Important update 1: Email Support is being transitioned to Webforms. Click here for more information.
Recent Searches

No recent searches

    Popular Articles

      Articles
      View all
        Topics
        View all
          Tickets
          View all
            no results

            Sorry! nothing found for

            Troubleshooting the Enom API

            Most API errors provide enough information in their error messages to resolve them. A few errors appear frequently when you set up API access. This article describes the most common error types and how to fix them.

            Where to find error definitions

            The API error codes have detailed descriptions on the API documentation page, as do the registry-registrar protocol (RRP) response codes. A few errors appear frequently when setting up API access.

            Tip: If you see a timeout, try the call again after a few minutes.

            Common error types

            Error typeExample error messageWhat it meansHow to resolve
            Validation errorErrCount=1 Err1=Bad User name or Password ResponseCount=1 ResponseNumber1=304155 ResponseString1=Validation error; invalid ; loginidThe login credentials are not valid.
            • Make sure your call uses the correct API token and login ID.
            • Check whether the credentials were for the live environment (reseller.enom.com) or the test environment (resellertest.enom.com). Different tokens or passwords are used for the live and test environments.
            Validation errorErr1=Invalid Registrant information. Err2=Parameter value range error - 7037 - Invalid telephone number format. ResponseCount=1 ResponseNumber1=304145 ResponseString1=Validation error; invalid ; registrant contact Note: other contact validation errors provide similar responses.The information being submitted does not comply with the domain's registration requirements.
            • The error code response string explains the cause of each error.
            • The RRP response codes (200, 210, 541) can also provide information about a particular API call.
            • Ensure the data submitted adheres to the registry's requirements for particular TLDs.
            IP errorErrCount=1 Err1=User not permitted from this IP address - [the IP address doing the call]. See Whitelisting your IP for the live environment for details. ResponseCount=1 ResponseNumber1=713254 ResponseString1=Policy error; unauthorized; user(s)The IP address performing the API call has not been added to the Enom account.
            SSL errorErrCount=2 Err1=500 - Unable to parse CSR. Err2=Unable to retrieve CSR information ResponseCount=2 ResponseNumber1=620397 ResponseString1=System error; failed to send; ResponseNumber2=304224 ResponseString2=Validation error; invalid ; informationThe example error indicates an issue with the CSR formatting.
            • Check your CSR using a CSR decoder tool.
            • Ensure your CSR is properly formatted and encoded for the API call.
            • Other errors show which part of the call is causing the issue.
            Other errorErrCount=1 Err1=Failed executing CERTPARSECSR ResponseCount=1 ResponseNumber=699999 ResponseString=System error; unknown; unknownThere may be an issue with the connection to a particular upstream provider or an internal problem with the Enom system.
            • These errors can often be transient. First, attempt the call again after a few minutes.
            • If the error persists, contact support for further investigation. Include the complete API call and server response in your support request.

            Next steps

            Questions? Contact Enom Support.

            How helpful was this article?

            Thanks for your feedback!

            Do you still need help? If so please submit a request here.