Functional Change: Validating email IDs in Zoho Desk REST APIs

Functional Change: Validating email IDs in Zoho Desk REST APIs

Dear Zoho Desk API users,

As part of our continuous API enhancement efforts, we are introducing a bunch of validation rules for email IDs that are passed in our REST APIs. 

Until now, only basic validation of email IDs was being carried out in our APIs. Going forward, a few other conditions will also be checked while processing API requests. 

The email ID passed through the API request will not be accepted if:
  • The username contains two consecutive periods. 
    Example: doug
    ..mendoza@emailbox.com
  • A period exists just before the @ symbol. 
    Example: doug.mendoza.@emailbox.com
  • The domain portion contains the _ symbol. 
    Example: doug.mendoza@email_box.com
If the email ID in the API request fulfills any of the above conditions, an error will be returned, stating that the email ID will not be accepted. 

The APIs that will be impacted due to this change are:
  • /api/v1/accounts
  • /api/v1/accounts/([0-9]+)
  • /api/v1/contacts/addMany
  • /api/v1/contacts
  • /api/v1/contacts/([0-9]+)
  • /api/v1/tickets
  • /api/v1/tickets/([0-9]+)
  • /api/v1/chatTicket
  • /api/v1/chatTicket/([0-9]+)/thread
  • /api/v1/imports

We request you to review your API-based tools and tweak them to accommodate this change. This change will be in effect from the 30th of June, 2021. Therefore, we request you to make the changes where necessary, as soon as possible. 

For any questions and clarifications, contact us at support@zohodesk.com

Thank you!