API Status Codes
The success or failure of an API request is conveyed by the code and message in its response. The following table lists all the codes corresponding to Zoho Creator's REST APIs.
HTTP Status Code | HTTP Status | Code | Message | Description |
---|---|---|---|---|
200 | OK | 4000 | Account's Developer API limit has been reached. Please upgrade to execute more REST API calls. | The Zoho Creator subscription dictates the number of REST API requests that can be made per day. You'll have to check the Creator account's usage details and either upgrade its Developer API limit or wait a day to make the next API request. |
200 | OK | 3970 | A maximum of 200 records can be fetched per request. | The get records API can fetch up to 200 records per request. You'll have to use the from parameter in your requests to fetch records 1-200, 201-400, and so on. |
200 | OK | 3960 | A maximum of 200 records can be processed per request. Include the "process_until_limit" parameter to process the first 200 records. | A maximum of 200 records can be updated or deleted per request. Including process_until_limit=true in the update records and delete records API requests tells the request server to perform the update or delete operation for the first 200 records that match the given criteria. You'll have to loop your API requests until the more_records key in the response is returned as false. |
200 | OK | 3950 | A maximum of 200 records can be added per request. | The add records API can add up to 200 records per request. You'll get this error when the number of JSON objects in the request body exceeds 200. We recommend breaking down your input accordingly. |
200 | OK | 3930 | No reports available. | The target application does not have any reports. |
200 | OK | 3920 | No pages available. | The target application does not have any pages. |
200 | OK | 3910 | No forms available. | The target application does not have any forms. |
200 | OK | 3830 | You do not have permission to transfer files to/from the field "<FIELD_NAME>". Please check with the application admin. | The requesting user does not have permission to upload a file to the target file upload, image, audio, video or signature field since they don't have permission to add/update records in that form. |
200 | OK | 3780 | No subform named "<LINK_NAME"> found. Please check and try again. | The target form does not contain a subform with the given link name. You need to check the target form and use the correct field's link name in the API request. |
200 | OK | 3750 | "<LINK_NAME>" is not a file type field. Please check and try again. | The field link name given in the request does not belong to a file upload, image, audio, video or signature field in the target report. You need to check the corresponding form and use the correct field's link name in the API request. |
200 | OK | 3730 | No file found in the record with ID "<RECORD_ID>". | Either there's no file in the target file upload, image, audio, video, or signature field, or it contains a file of size 0 KB. |
200 | OK | 3710 | No field named "<LINK_NAME>" found. Please check and try again. | No field named "<LINK_NAME>" found. Please check and try again. |
200 | OK | 3660 | No file found in the request. Please include a file and try again. | The upload file API request does not have a file in it. An input file is required to perform the upload operation. |
200 | OK | 3630 | Input file exceeds the 50 MB limit. Please upload a smaller file. | The file upload field can accept a file that doesn't exceed 50 MB. The upload file API request will fail so when the input file exceeds this limit. |
200 | OK | 3190 | No record with ID "<RECORD_ID>" found. | There is no record in the target form with the given record ID. |
200 | OK | 3120 | For the lookup field: For the drop down field: | If the target field is of type lookup, then you've not passed it an integer value. If the target field is of type drop down, then you've not passed it a text or string value. |
404 | NOT FOUND | 3100 | No records found for the given criteria. | There are no records in the target form/report that match the given search criteria. You may search using different criteria if required. |
404 | NOT FOUND | 3090 | When no criteria is passed: When an invalid criteria is passed: When a field's link name, that used in the criteria, is incorrect: | This concerns the API requests that allow a criteria to be passed so as to perform the required operation on select records. Either the request requires a criteria and one hasn't been given, or the criteria is invalid, or the link name of one of the fields used in the criteria is incorrect. |
200 | OK | 3070 | Data validation failure: "[ARRAY]" | This concerns the add and update record API requests. The add or update operation will be performed only when the input passes the data validations in place for the target form. The array will list the validations that the input data failed. You may refer to the "Data validations in Creator" section of the API documents. |
200 | OK | 3060 | Account's record limit has been reached. Please upgrade to add more data. | The Zoho Creator subscription dictates the total number of records that can be stored in the account. Unless you upgrade, further record creation won't be permitted. You can check the Creator account's usage details to view the limit. |
200 | OK | 3050 | Passing values for Formula, File Upload and Image type fields is not allowed. Use the Upload File API to update the File Upload and Image fields. | The add and update record APIs cannot assign a value for the formula, file upload, and image fields. The formula field's value is evaluated as per its expression and you must use the upload file API to upload a file to the file upload and image fields. |
400 | NOT FOUND | 3030 | API request's body is not properly formed. | The API request's body does not include a proper JSON input. |
400 | NOT FOUND | 3020 | API request's body is either missing or incomplete. | The API request's body content is missing. |
403 | FORBIDDEN | 3002 | The "<FEATURE_NAME>" feature is currently not available for this Zoho Creator account. Please contact support@zohocreator.com to learn more. | This error will occur when the requesting user is trying to perform an operation that is beyond the Creator account's subscription. Please refer to the pricing page for feature availability. |
403 | FORBIDDEN | 2965 | No more entries allowed as per the form validation. | The form is configured to be disabled after accepting a certain number of entries. Learn more |
401 | AUTHORIZATION ERROR | 2945 | ERROR | This is an invalid OAuth scope. Please regenerate the OAuth token corresponding to the API with the proper OAuth scope. |
403 | FORBIDDEN | 2933 | You do not have permission to access this application. | The requesting user does not have access to the target application. In other words, it hasn't been shared with that user. |
403 | FORBIDDEN | 2930 | Error Occurred. We are sorry for the inconvenience. | Please contact support@zohocreator.com to learn more. |
403 | FORBIDDEN | 2899 | Permission denied to add record(s). | The requesting user is not permitted to add records to the target form/report. |
403 | FORBIDDEN | 2898 | Permission denied to view record(s). | The requesting user is not permitted to view the records of the target form/report. |
403 | FORBIDDEN | 2897 | Permission denied to update record(s). | The requesting user is not permitted to update the records of the target form/report. |
403 | FORBIDDEN | 2896 | Permission denied to delete record(s). | The requesting user is not permitted to delete the records of the target form/report. |
404 | NOT FOUND | 2894 | No report named "<REPORT_NAME>" found. Please check and try again. | There's no report in the target application with the given report link name. You may use this reference document to view the link names of your applications and components within them. (Use the domain that corresponds to your Zoho account to access the reference document) |
404 | NOT FOUND | 2893 | No form named "<FORM_NAME>" found. Please check and try again. | There's no form in the target application with the given form link name. You may use this reference document to view the link names of your applications and components within them. (Use the domain that corresponds to your Zoho account to access the reference document) |
404 | NOT FOUND | 2892 | No application named "<APPLICATION_NAME>" found. Please check and try again. | There's no application in the target Creator account with the given application link name. You may use this reference document to view the link names of your applications and components within them. (Use the domain that corresponds to your Zoho account to access the reference document) |
403 | FORBIDDEN | 1130 | You do not have permission to access this application's APIs. Please check with the application admin. | The API access permission is disabled for the requesting user. If you want to give the requesting user this permission, you must either enable it in their permission set or you must assign them another permission set where the API access permission is enabled. |
403 | FORBIDDEN | 1100 | You do not have permission to access this component. Please check with the application admin. | The requesting user is not permitted to access the target component (form, report, or page). |
404 | NOT FOUND | 1090 | No component named "<COMPONENT_NAME>" found in this application. Please check and try again. | The link name of the component (form, report, page) given in the request is not valid. You may use this reference document to view the link names of your applications and components within them. (Use the domain that corresponds to your Zoho account to access the reference document) |
403 | FORBIDDEN | 1080 | API calls cannot be made to disabled applications. Please check with the application admin. | There may have been a change in the Creator subscription that caused the target application to be disabled. You need to access the Creator account's home page and enable the target application. |
403 | FORBIDDEN | 1060 | You do not have permission to access this application. Please check with the application admin. | The target application has not been shared with the requesting user. |
404 | NOT FOUND | 1040 | No account owner named "<OWNER_NAME>" found. | The account_owner_name in the API request is not valid. You must use the username of the user in whose account the request is to be made. |
401 | AUTHORIZATION ERROR | 1030 | Authorization Failure. The access token is either invalid or has expired. Please check your Zoho Account for more information. | The access token passed in the authorization header is not valid. It may have expired, in which case you need to refresh the access token. |
405 | METHOD NOT ALLOWED | 1020 | "<METHOD>" is not a valid method for this request. | You've used an incorrect HTTP method to make the API request. Zoho Creator's v2 APIs support using GET, POST, PATCH and DELETE. Please refer to the individual documents to learn which method is to be used. |
401 | AUTHORIZATION ERROR | 1000 | IAM Error | There was an error at the Identity Access Manager's (IAM) end. Please contact support@zohocreator.com to learn more. |
404 | NOT FOUND | 1000 | Invalid API URL format. | The URL of the API request is not valid. Please refer to the individual documents to learn about their format. |
200 | OK | 3000 | Message "Data Added Successfully" or the success message is configured by the user. | "Data Added Successfully" will be shown when the message key is either set to false or not been included in the API request. The form's message will be present in the response when a custom message is set and the API request includes message=true. |
429 | Too Many Requests | 2955 | You have reached your API call limit for a minute. Please try again after sometime. | The threshold limit for all v2 APIs is set at 50 calls/min. When the specified per min limit is reached, this error response will be displayed. |
200 | OK | 9030 | API looping to same component exceeded the specified limit of 1. | This concerns the incorrect usage of API calls to add data in the same form in the application. Assume Form A triggers a workflow and uses an API call on successful form submission to add another record to the same form. This cycle continues, allowing the workflow to run repeatedly in a loop, with data getting added to the same form endlessly. As a measure to stop this looping and avoid the subsequent performance dip, workflow execution will be limited to one loop, for actions that add records to the same form. That is, the workflow will only be triggered once. For repetitive workflow actions, or if there is a need for multiple actions, users should create functions and use them wherever required. This will avoid the need for unnecessary API requests. Please contact us at support@zohocreator.com. |
200 | OK | 9040 | API looping to other component exceeded the specified limit of 3. | This concerns the incorrect usage of API calls to add data between different forms in the same application. There are two related forms—A and B. On successful submission of Form A, an API call is used to add a record in Form B, which in turn hits another API call, submitting another record in Form A and continuing the same pattern, adding records in both the forms over and over again. As a measure to stop this looping, workflow execution will be limited to three loops for actions that add records to other forms. That is, the workflow will be triggered thrice, allowing records to be added in three forms, after which it will cease to trigger. For repetitive workflow actions, or if there is a need for multiple actions, users should create functions and use them wherever required. This will avoid the need for unnecessary API requests. Please contact us at support@zohocreator.com. |