HTTP Status Code
|
HTTP Status
|
Code
|
Message
|
Description
|
403
|
FORBIDDEN
|
4000
|
Account's custom API limit has been reached. Please upgrade to execute more custom API calls.
|
The custom API could not be executed since the API call limit for the day has been exhausted. This limit will be displayed in the Billing module. The custom API can be invoked after waiting a day, or the account's API call limit can be extended by the super admin.
|
400
|
BAD REQUEST
|
9350
|
Custom API doesn't exist. Please check the custom API link name.
|
The custom API link name mentioned in the API request is incorrect or does not exist. The link mentioned here should match the one specified in the endpoint URL of the custom API:
|
400
|
BAD REQUEST
|
9360
|
Custom API is in draft or disabled state. Please enable the API and try again.
|
The custom API mentioned in the API request is either in the draft stage or has been disabled. The custom API's configuration has to be complete and enabled before executing the API request.
|
401
|
AUTHORIZATION ERROR
|
9370
|
The request contains an invalid public key for this Custom API.
|
The public key used in the API request is incorrect. Ensure that the exact public key from the summary of the custom API's configuration is specified here.
|
401
|
AUTHORIZATION ERROR
|
9380
|
You do not have permission to invoke this Custom API. Please reach out to the admin.
|
The user does not have permission to invoke this custom API, as it is restricted to admins of the organization where it was built. The user scope configuration defines which users are authorized to access the API, and it has been set to 'Admin Only.'
|
401
|
AUTHORIZATION ERROR
|
9390
|
You do not have permission to invoke this Custom API. Please reach out to the admin.
|
The user does not have permission to invoke this custom API since they have not been included in the user scope. The user scope, configured while building this custom API, defines which users are authorized to access the API.
|
405
|
METHOD NOT ALLOWED
|
9400
|
The provided HTTP method is not valid for this custom API.
|
The HTTP method does not match the expected request method with which this custom API was configured. The exact value from the summary of the custom API's configuration must be specified here.
|
400
|
BAD REQUEST
|
9410
|
The Content-Type specified for this Custom API is invalid.
|
The content type does not match with this custom API's configuration. The exact value from the summary of the custom API's configuration must be specified here.
|
500
|
INTERNAL SERVER ERROR
|
9430
|
There is an error while executing Custom API.
|
The custom API could not be executed since there is an error in the configured Deluge function. Ensure that any such errors are rectified before executing it again.
|
400
|
BAD REQUEST
|
9450
|
Datatype mismatch encountered. Please provide a valid value for %s.
|
The value entered for the specified key, '%s', does not match the datatype required for it. The datatype mentioned for the key in the request body should be followed here.
|
500
|
INTERNAL SERVER ERROR
|
9460
|
The action associated with this custom API does not align with the configurations for Request or Response. Please reach out to the admin.
|
|
401
|
AUTHORIZATION ERROR
|
9470
|
You do not have permission to invoke this Custom API since you have not accepted the invitation yet. Please check your email or reach out to the admin.
|
The user who invoked this custom API is restricted from performing that action. This is because they are a pending user in the account where the API was built. When an admin or super admin has added a user to an organization, they are added as a pending user. They have to accept the invitation sent by the admin to become a confirmed user, after which they can invoke this API.
|
401
|
AUTHORIZATION ERROR
|
9480
|
The specified user does not exist.
|
The user who has invoked this custom API does not belong to the organization in which it has been created.
|
401
|
AUTHORIZATION ERROR
|
9490
|
The specified user is currently inactive. To activate, please reach out to the admin.
|
The user who has invoked this custom API is inactive in the organization in which it was created. They have to be activated by an admin or super admin, after which they can invoke this API.
|
500
|
INTERNAL SERVER ERROR
|
9500
|
Invalid Custom API configuration. Please reach out to the admin.
|
The API request could not be executed due to an error in the custom API's configuration. The correctness of the custom API configuration and whether it is ready to be invoked should be checked.
|
403
|
FORBIDDEN
|
9510
|
Invalid domain name. Kindly use the domain - %s
|
The custom API could not be executed since the domain mentioned in the endpoint URL is invalid. The endpoint URL must specify the domain as mentioned in the error message.
|
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.