Data Storage APIs

Get data

• key - Helps to identify what is being called by the API.
• queriableValue - Specifies a common lookup group which will be useful for lookup from the database.

Set data

• The value passed by key can have a maximum length of 50 characters. The only special characters allowed are commas (,), underscores (_), and colons (:). The value of this parameter cannot be NULL.
  
• The data passed by value must be a JSON object whose size cannot exceed 1 KB. Empty JSON objects can be passed, too. 
  
• The value passed by queriableValue can have a maximum length of 50 characters. The only special characters allowed are commas (,), underscores (_), and colons (:). The value of this parameter can be NULL.

Delete data

• Use ZOHODESK.request to invoke Zoho Desk's "Create Events" API.
  Here, we are pushing the event data into Zoho Calendar.
• Construct the request object for ZOHODESK.request.
  
  {

      "url": "https://calendar.zoho.com/api/v1/calendars/calId/events",

      "type": "POST",

      "headers": {},

      "postBody": {},

      "connectionLinkName": "calendarEvent",

      "data": {

          "eventdata": {

              "dateandtime": {

                  "timezone": "Asia/Kolkata",

                  "start": "20220225T130000+0530",

                  "end": "20220225T133000+0530"

              },

              "title": "Today's morning meeting"

          }

      }

  }
• Extract the required values from the response of the request.
  
• Use ZOHODESK.set to invoke Zoho Desk's "set record" API.
  

  ZOHODESK.set("database", {

      "key": userId,

      "value": {

          "eventId": eventData.id

      },

      "queriableValue": "eventIds"

  })

• Creating events in Zoho Calendar by making a call to the Calendar events API, post method. The Request API SDK of Zoho Desk is used to invoke the Zoho Calendar API. The events are created with event date, event start time, and end time, with the time zone defined.
  
• As mentioned, we need to list those events in our extension for our quick reference, so the required event information is fetched from the Request API's response.
  
• Finally, we're storing the event information in our extension database using the set method. Here, we have defined key as userId, value as eventData.id, and queriableValue as eventIds. So all the events (eventData.id) created by the user (userId) will be stored within the database (eventIds).