The Zoho Desk resources, such as Tickets, Contacts, Tasks, etc. The following are some terms you need to know before you start using the Zoho Desk APIs. If the client faces a security breach, user data will be compromised only until the access token is valid. OAuth2.0 access tokens expire after a set time. Users can revoke the client's delegated access anytime.
ZOHO OUTLOOK TICKETING PASSWORD
Why should we use OAuth2.0?Ĭlients are not required to support password authentication or store user credentials.Ĭlients gain delegated access, i.e., access only to resources authenticated by the user.
ZOHO OUTLOOK TICKETING CODE
To view a sample reference code in Java to help you understand the OAuth authorization flow for Zoho Desk Rest APIs, click here. Each API request must include an OAuthToken to retrieve any resource from your Zoho Desk portal. This protocol delegates user authentication to the service that hosts the user account and authorizes third-party applications to access the user account. Zoho Desk's APIs use the industry-standard OAuth 2.0 protocol for authentication and authorization. This errorCode value appears if the server encounters an unexpected condition that prevents it from fulfilling the request. This errorCode value appears if the user sends too many requests within a given amount of time ("rate limiting"). The integration param returns the integration the user enabled in the portal. This errorCode value appears if the API request tries to deactivate a user who has enabled integrations in the help desk portal This errorCode value appears if the API request tries to remove the last user remaining in a department that has live chat enabled INTEGRATION_ADMIN_ERROR
This errorCode value appears if the input does not fulfil the conditions necessary for successfully executing the API. The field that contains the inaccurate value is returned in the fieldName param, which is represented in the JSON Pointer convention UNPROCESSABLE_ENTITY
The type of inaccuracy is identified by the errorType param. This errorCode value appears if there are inaccuracies, such as duplicate entries or invalid IDs, in the data given by the user. This errorCode value appears if the server refuses the request as a result of receiving the input in an unsupported format. This errorCode value appears if the size of the resource exceeds the limit defined by the server. This errorCode value appears if the method in the API request is known by the server but disabled for the API requested. This errorCode value appears if the URL provided is invalid or does not exist. The possible values for the editionType key are The possible values for the feature key are This errorCode value appears if the user is unable to perform an action due to the limitations of the Zoho Desk edition in use This errorCode value appears if the user does not have all the permissions required to access the resource. This errorCode value appears if the user chooses a different organization while generating the OAuthToken instead of the organization in which they want to perform the operation. This errorCode value appears if the OAuthToken does not contain the scope required to perform the operation. This errorCode value appears if the OAuthToken is invalid or expired. This errorCode value appears if the authentication token in the API request is invalid INVALID_OAUTH The different errorCodes and their uses are described below.
Method not allowed (Method called is not supported for the API invoked)īesides HTTP status codes and their corresponding error messages, error responses for Zoho Desk APIs also include a machine-parsable errorCode param to simplify error handling. The following table lists some commonly used HTTP status codes. Status codes in the 2xx range indicate success, 4xx range indicate error in the information provided, and 5xx range indicate server side errors. Zoho Desk uses HTTP status codes to indicate success or failure of API calls.
0 kommentar(er)
