Kaizen #7 - URL Encoding while making API Calls
Welcome to another week of Kaizen. In this post, we will discuss things you need to handle in your code before you start making API calls to Zoho CRM.
If you have an application that is integrated with Zoho CRM, it will contain the code for making API calls with different request methods—GET, POST, PUT, and DELETE. We will explain the things you need to handle for each of these methods, before you use it to make API calls to Zoho CRM.
a. GET method
A GET method is used to retrieve data/resource from the resource server. For example, Search Records.
For the GET method, you need to pass data as a parameter in the request URL, and that parameter value has to be URL encoded.
URL encoding is a way to encode or escape reserved, unprintable, or non-ASCII characters in URLs, and convert them into a secure format.
Consider the following example, when you try to search a lead record with an email ID(p.daly+demo1@zylker.com).
When this request URL is decoded in our end, it gets converted into:
The '+' character got decoded as 'space'. Because, the '+' character is valid in URL as a substitute for space. Therefore, they have to be encoded or escaped. If not, the URL might be misinterpreted while decoding it.
Unsafe characters that you need to encode are the following.
- ASCII Control characters:
ISO-8859-1 (ISO-Latin) character ranges 00-1F hex (0-31 decimal) and 7F (127 decimal.) - Non-ASCII characters:
Entire “top half” of the ISO-Latin set 80-FF hex (128-255 decimal.) - Unsafe characters
Blank/empty space and " < > # % { } | \ ^ ~ [ ] ` - Reserved characters when NOT USED for their reserved or defined purposes such as / ? : = &.
Based on your language, you can use the following methods to encode the reserved characters.
Language | Script |
Java | URLEncoder.encode("(p.daly+demo1@zylker.com)", "UTF-8"); |
Ruby | URI::encode("(p.daly+demo1@zylker.com)") |
PHP | urlencode("(p.daly+demo1@zylker.com)") |
Python | urllib.parse.quote("(p.daly+demo1@zylker.com)".encode("UTF-8")) |
After encoding, the resultant search query will have the following email ID—p.daly%2Bdemo1%40zylker.com
The corresponding cURL code for this operation is:
curl -X GET \
-H 'Authorization: Bearer 1000.b481413bedf852e81bf591e7ca769de8.85f9671a36047d740216b656c8b3ad4d'
You can see that the data in the URL is encoded.
b. POST/PUT method
POST method is used to insert or upload any new resources to the server. For example, Insert Records.
PUT method is used to update an existing resource. This replaces the target resource with the updated content. For example, Update Records.
You can pass the input data for an API call in different ways, based on API requirements.
- Sending data as parameter in the request URL
- Sending data wrapped in a request body
Let us look into each of these methods.
a. Sending data as a parameter in the request URL
As mentioned in the earlier section, when you send data as a parameter in the request URL, it has to be encoded.
b. Sending data wrapped in a request body
When data is sent in request body, it is secure. There are two different methods in which you can send data wrapped in a request body, for an API call. Based on the API requirement, you can choose the appropriate method.
- Sending data as raw JSON in the request body
In this type, the data is sent as JSON in the request body. Here, you need to add the header 'Content-Type' as 'application/json'. When data is sent as raw JSON, it need not be encoded. - Sending data as a key-value pair
Here, the data is given as key-value pairs. For instance, while you upload an attachment, you need to send the file data, for which you need to make the request with 'Content-Type' as 'multipart/form-data'. Here the data is wrapped in request body. Therefore, it need not be encoded. If the data you have is already encoded, you must use the 'application/x-www-form-urlencoded' content-type and you cannot send file data with this content-type.
Consider the following example of inserting leads.
The corresponding cURL code is:
-H 'Authorization: Bearer 1000.b481413bedf852e81bf591e7ca769de8.85f9671a36047d740216b656c8b3ad4d' \
-H 'Content-Type: application/json' \
-d '{
"data": [
{
"Company": "Zylker",
"Last_Name": "Daly",
"First_Name": "Paul",
"Email": "p.daly+demo1@zylker.com",
"State": "Texas"
},
{
"Company": "Villa Margarita",
"Last_Name": "Bran",
"First_Name": "Hofstadter",
"Email": "bran.h+demo2@villa.com",
"State": "Texas"
}
],
"trigger": [
"approval",
"workflow",
"blueprint"
]
}'
You can see that the data is not encoded.
c. DELETE method
DELETE method is used to delete a resource at a particular location. For example, Delete Records.
URL encoding for the DELETE method is the same as the GET method. Consider the following example of deleting leads.
Encoded request URL:
https://www.zohoapis.com/crm/v2/Leads?ids=4150868000000843062%2C4150868000000843044
We hope you found this post useful. Keep a tab on this series for more exciting topics!
Reach out to us at support@zohocrm.com if you have any questions, or let us know in the comment section.
Cheers!
Previous 'Kaizen' - Environments and Domains in Zoho CRM [Part2/2]
Access your files securely from anywhere
Zoho Developer Community
New to Zoho LandingPage?
Zoho LandingPage Resources
New to Zoho Survey?
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Bigin?
Topic Participants
Sneha Sridharan
Sticky Posts
Kaizen#162 : Add Tags and Open Pre-filled Email Drafts via Client Scripts
Hello everyone! Welcome to another informative Kaizen post. In this post, let us see how to accomplish the following using Client Script. 1. How to auto-tag a record based on field update? 2. How to Open a pre-filled email draft This post will provideClient Script | Update - Introducing Commands in Client Script!
Have you ever wished you could trigger Client Script from contexts other than just the supported pages and events? Have you ever wanted to leverage the advantage of Client Script at your finger tip? Discover the power of Client Script - Commands! CommandsExtension Pointers - JS SDK series #4: Managing data from a widget using ZOHO.CRM.HTTP
Handling and managing the data between two applications is a major factor for an efficient business. There are a variety of ways to handle data between Zoho CRM and other third-party applications. You can use deluge CRM tasks, create connectors, use APIKaizen #152 - Client Script Support for the new Canvas Record Forms
Hello everyone! Have you ever wanted to trigger actions on click of a canvas button, icon, or text mandatory forms in Create/Edit and Clone Pages? Have you ever wanted to control how elements behave on the new Canvas Record Forms? This can be achievedExtension pointers for integrating Zoho CRM with Zoho products #8: Upload and manage Zoho Workdrive folders and files from within Zoho CRM
Keeping records on your customers and business prospects is essential for tracking data, conducting follow-ups, and running a business smoothly. When you use two separate applications, and store relevant data in each, checking and tracking data becomes
New to Zoho TeamInbox?
Zoho TeamInbox Resources
Zoho DataPrep Resources
Zoho CRM Plus Resources
Zoho Books Resources
Zoho Subscriptions Resources
Zoho Projects Resources
Zoho Sprints Resources
Qntrl Resources
Zoho Creator Resources
Zoho Campaigns Resources
Zoho CRM Resources
Design. Discuss. Deliver.
Zoho Show Resources
Get Started. Write Away!
Writer is a powerful online word processor, designed for collaborative work.
Zoho CRM コンテンツ
-
オンラインヘルプ
-
Webセミナー
-
機能活用動画
-
よくある質問
-
Ebook
-
-
Zoho Campaigns
- Zoho サービスのWebセミナー