Last updated: September 12, 2019
Code | Description |
---|---|
0 - Internal Failure | Something went wrong on FreeClimb's end. Either a service was inaccessible or was configured wrong. Our engineers are hard at work resolving this problem. |
1 - Not Found | You tried to reference a resource that doesn't exist. To fix the issue, try: 1. reviewing the Resources list in the Overview of FreeClimb 2. checking for any typos or misspellings |
2 - Method Not Allowed | You attempted to use a method not allowed for a particular resource. To fix the issue, try: 1. reviewing the available methods for the resource under the API Reference 2. check for any typos or misspellings |
3 - Bad Request Body | Message: Request Body Could Not Be Read The request you made couldn't be parsed as a valid JSON payload. To fix the issue, try: 1. Reviewing the documentation to ensure you've encoded the request correctly 2. Including the Content-Type header in the request |
4 - PQL Field Empty | Performance Query Language is a required field. To fix the issue, try adding correctly-formatted PQL |
5 - Invalid PQL | The Performance Query Language (PQL) entered is invalid. To fix the issue, try checking that your PQL is correctly formatted |
6 - Account Unusable | Your account is currently unusable. To fix the issue, try: 1. updating your profile to ensure you have the correct information on file 2. contacting support if the the problem persists |
7 - Cannot Resolve Number | FreeClimb is unable to resolve the phone number which was used. To fix the issue try: 1. making sure that you have entered a valid phone number in the E.164 format. 2. ensuring your number is voice enabled. |
8 - Invalid PerCL | The PerCL script received from your application is invalid. To fix the issue try: 1. reviewing PerCL documentation to ensure your PerCL is correct 2. checking how your framework and/or package renders responses if your JSON formatting is incorrect |
9 - Invalid JSON | You have sent an invalid JSON object as part of the request. To fix the issue try: 1. revalidating your JSON and trying the request again 2. checking your PerCL for incorrect formatting or typos |
10 - Number Not SMS Enabled | You have tried to send an SMS with a number that is not SMS enabled. To fix the issue, try: 1. using a different number to send an SMS 2. confirming the number is 10DLC and/or TFN SMS-enabled |
11 - International SMS is Forbidden | International SMS is not allowed for the phone number used. To fix the issue, try: 1. using a phone number which supports international SMS. For further information about 2. adding international SMS numbers to your account, please contact support |
12 - Error Posting to Application | FreeClimb received an error response from the application server. To fix the issue, try: 1. ensuring you have used the correct URLs on the "Apps" page on your FreeClimb dashboard 2. checking the webhooks documentation to ensure your webhooks are set up correctly |
13 - Empty PerCL | PerCL script parameters cannot be empty. To fix the issue, try checking that you have used PerCL in all necessary parts of your application |
14 - Too Many Redirects | FreeClimb has detected too many redirects in your application. To fix the issue, try ensuring that there are no loops in your application |
15 - Failed to Create Calling Number | The system was unable to create a calling number. This is an internal error. If the error persists, please contact support. |
16 - Failed to Create a Call | The system was unable to create a call. This is an internal error. If the error persists, please contact support . |
17 - Failed to Update Call | The system failed to update the call. This is an internal error. If the error persists, please contact support. |
18 - Failed to Update Participant | The system was unable to update a participant in the conference. This is an internal error. If the error persists, please contact support. |
19 - Failed to Hangup Participant | The system was unable to hangup a participant from the call. This is an internal error. If the error persists, please contact support. |
20 - Failed to Delete Participant | The system failed to delete a participant from the conference. This is an internal error. If the error persists, please contact support. |
21 - Code Expired | Your verification code for adding a verified number has expired. To fix the issue, try requesting a new verification code in the dashboard |
22 - Wrong Code | The verification code you entered does not match the one we sent you. To fix the issue, try: 1. verifying again with the correct code 2. requesting a new code if the issue persists |
23 - Number Already Verified | You've attempted to verify a phone number that's already been verified. To fix the issue, try verifying a different number. To view already verified numbers associated with your account, visit the Verified Numbers page in your dashboard. |
24 - Request Sent Too Early | You attempted to perform an action before waiting an appropriate amount of time. To fix the issue, try waiting for a short period of time and trying again. If the error persists, please contact support . |
27 - Account Type is Full | You attempted to perform an operation that does not match your account type. This error may be related to the verified number functionality found in our free trial accounts which so longer applies to upgraded accounts. To fix the issue, try: 1. removing any functionality in your application associated with a free trial account 2. reviewing the permissions associated with a free trial account |
28 - Invalid Code | The code you entered to validate the outbound phone number was incorrect. To fix the issue, try: 1. checking that you have entered the correct code 2. requesting a new code if the issue persists |
29 - Phone Number Not Verified | Your account is in trial mode and the number you tried to call or message wasn't a verified phone number. To fix the issue, try checking that the outbound number you are using is verified in the dashboard. |
30 - Account Suspended | Your FreeClimb account has been suspended. To fix the issue, try contacting support for more information. |
31 - Max Attempts Reached | The maximum attempts were reached for performing the given operation. If the issue persists, try contacting support for more information. |
32 - Recaptcha Verification Failed | There was an error while verifying the captcha. To fix the issue try doing the captcha again. If the error persists, please contact support. |
33 - Account Locked Out | Your account has been locked temporarily. To fix the issue, try logging into your account again later. If the error persists, please contact support. |
34 - Account Already Exists | You may have attempted to create an account with an email that is already in our database. To fix the issue, try signing up again with a different email address. If the error persists, please contact support. |
35 - Problem Creating Account | There was an unspecified problem creating the account. To fix the issue, try creating your account again. If the error persists, please contact support. |
36 - Email Invalid | The email included in the request made is not valid. To fix the problem, try checking the format of the email address and trying the request again. |
37 - Error Sending Email | There was a problem sending an email. To fix the issue, try: 1. checking all the fields to make sure they are correct 2. resending the email |
38 - Code Missing | The request did not include the Code parameter that is required for the verification. To fix the issue, try: 1. checking that your code is the correct length 2. requesting a new code |
39 - Invalid Password Reset Attempt | Your password reset attempt is invalid. To fix the issue, try checking to see if your reset code has expired. If the error persists, please contact support. |
40 - Invalid Credentials | You have tried to login with an invalid email or password. To fix the problem, try checking your credentials and trying the request again. |
41 - Terms of Service Already Accepted | You have already accepted the terms of service. |
42 - Not Logged In | You are not logged into FreeClimb. To fix the problem, try checking your credentials and logging in again. |
43 - Unrecognized Account Type | Your account type is not recognized by our system. This is an internal error. If the error persists, please contact support. |
44 - Unrecognized Account Status | Your account status is not recognized by our system. This is an internal error. If the error persists, please contact support. |
45 - ApiKey Cannot Be Empty | The API key must be provided. |
46 - Phone Number Not Usable | The phone number is not usable by your account. This phone number may not be owned by your account or is not voice enabled. |
47 - International Call Forbidden | You do not have access to international calls. |
48 - Resource Not Ready | The resource you have requested is not available at this time. |
49 - SMS Not Enabled | SMS is not enabled for this account. |
50 - Unauthorized | You are unauthorized to make this request. |
51 - Account Closed | The account is closed. |
52 - Service Unavailable | A service is unavailable. |
53 - Invalid Endpoint | The webpage does not exist. |
54 - Bad Password | The password you have entered is incorrect. |
55 - Maintenance Mode | The server is in maintenance mode. |
56 - Call Already In Conference, Cannot Add to Queue | The Call is already in a Conference and cannot be added to a Queue. To fix the problem, try waiting until the Call is no longer in a Conference. |
57 - Account in file URL Does Not Match with Requesting Account | The account contained in the file FreeClimb URL does not match your account. To fix the problem, try using a file FreeClimb URL which matches your account. |
58 - Queue Command Invalid | Only play, say, pause, getDigits, dequeue, hangup, sendSipInfo, sendAppOutcome, sendAppNav, and redirect allowed while in queue. To fix the problem, try removing any disallowed PerCL commands from your script. |
59 - Failed to Create a Queue | The system was unable to create a Queue. This is an internal error. If the error persists, please contact support. |
60 - Queue is Full | The Queue is full. To fix the problem, try: 1. ensuring Calls are being dequeued properly in order to remain under the max Queue size 2. allocating a larger Queue size in the future |
61 - Attempted Reuse of Resource ID | An attempt was made to reuse a resource ID. This is an internal error. If the error persists, please contact support. |
62 - Failed to Create Conference | The system was unable to create a Conference. This is an internal error. If the error persists, please contact support. |