Response title
This is preview!
- Search All
- Tags
- Author
- Advanced Search
Move this topic
We are very happy to announce the GA release of API for Zoho CRM service. Our API is available in XML and JSON formats, which helps the developer community to build applications using their favorite programming language (such as Java, C, C++, PHP, Python etc.). Now we are ready with robust and much better API methods to cater to the needs of real-time deployments. Your valuable contribution towards identifying bugs, coming up with new business scenarios and publishing examples really helped us to come up with a better API for our CRM system.
In addition to the GA release, we are also making some major changes in our existing API implementation that allows us to fulfill the future needs of our developer community. Some of these changes include, deprecation of search methods, new response format, restriction of API requests and new API methods for implementing additional CRM business logic. We sincerely believe, these changes will greatly help us to provide a better experience to the developer community and take Zoho CRM developer platform to the next level.
1. Deprecation of API Methods
Keeping the future community growth, better developer service and optimization of the high performance-intensive operations in view, we are phasing out the following API methods:
Of late, we are encountering a huge amount of resource utilization while implementing the getAllSearchRecords and getMySearchRecords than expected. To overcome this kind of situation, we are introducing new search methods, getSearchRecords and getSearchRecordsByPDC , which serves the similar purpose. We have optimized these new methods for better performance.
Note:
At present, XML format for the API response is <fieldlabel value="LEADID">Field Value</fieldlabel>, which contains about 26 characters (including space) in the opening and closing tags. In our new implementation, we have shortened the tag size by changing the XML tags to <FL val="LEADID">Field Value</FL> - total 8 characters, which saves about 18 bytes per field. This will greatly help us to optimize the utilization of bandwidth.
Till Dec 7, 2009, by default, you will get the response in the old format. If you want to get the response in the new format, you must pass the extra argument with newFormat=1 or 2 in API request.
Old Format:
New format:
Key Points:
From Dec 07, 2009 (12.00 AM PST), you can request API calls as per your Zoho CRM Edition. In case, your application requires more than upper limit, your additional API requests will not be processed. To avoid data transfer issues, please assess your API requirements well in advance. If you need any help, please contact our Support at support@zohocrm.com or call us:+1 888 900 9646.
We are really excited to introduce the following new methods for the benefit of growing developer community:
We are confident, the above methods will be very useful in implementation of search functions and allows you to develop additional business logic through our API. These methods will be made available for all editions immediately.
In addition, we are incorporating the following minor changes:
Thank you in advance for your kind cooperation.
Best Regards,
Gopal
(Team Zoho CRM)
UPDATE on Nov 26, 2009:
Extended End of Life Date for another 45 days - from Dec 07, 2009 to Jan 21, 2010. Now the total duration is 90 days.
In addition to the GA release, we are also making some major changes in our existing API implementation that allows us to fulfill the future needs of our developer community. Some of these changes include, deprecation of search methods, new response format, restriction of API requests and new API methods for implementing additional CRM business logic. We sincerely believe, these changes will greatly help us to provide a better experience to the developer community and take Zoho CRM developer platform to the next level.
Important Changes
- Deprecation of existing search methods - getAllSearchRecords and getMySearchRecords
- Implementation of new response format for all the methods
- Restriction of API requests based on the Zoho CRM edition
- Introduction of new methods for Search, Lead Conversion and Delete functions
1. Deprecation of API Methods
Keeping the future community growth, better developer service and optimization of the high performance-intensive operations in view, we are phasing out the following API methods:
- getAllSearchRecords
- getMySearchRecords
| API Method | Purpose |
| getAllSearchRecords | Used to fetch all data with respect to the search word specified irrespective of the ownership. |
| getMySearchRecords | Used to fetch data owned by the loginname with respect to the search word specified in the request. |
| getAllRecords | Name has been changed to getRecords |
| getEntityRecord | Name has been changed to getRecordById |
Of late, we are encountering a huge amount of resource utilization while implementing the getAllSearchRecords and getMySearchRecords than expected. To overcome this kind of situation, we are introducing new search methods, getSearchRecords and getSearchRecordsByPDC , which serves the similar purpose. We have optimized these new methods for better performance.
End of Life: December 07, 2009 |
Note:
From Dec 7, 2009 (12.00 AM PST) these methods will be nonfunctional and if you still use them, system will throw the following error message in your application:
Unable to process your request. Kindly verify whether you have entered proper method name, parameter and parameter values.
Important Note:
Before end of life, you are strongly recommended to update your application with the new search methods - getSearchRecords or getSearchRecordsByPDC . For any help or clarification, please mail us at: support@zohocrm.com
2. New Response Format
At present, XML format for the API response is <fieldlabel value="LEADID">Field Value</fieldlabel>, which contains about 26 characters (including space) in the opening and closing tags. In our new implementation, we have shortened the tag size by changing the XML tags to <FL val="LEADID">Field Value</FL> - total 8 characters, which saves about 18 bytes per field. This will greatly help us to optimize the utilization of bandwidth.
Till Dec 7, 2009, by default, you will get the response in the old format. If you want to get the response in the new format, you must pass the extra argument with newFormat=1 or 2 in API request.
| Parameter | Purpose |
| newFormat=1 | To exclude fields with "null" values while fetching data from your CRM account. |
| newFormat=2 | To include fields with "null" values while fetching data from your CRM account. |
Old Format:
- <response uri="/crm/private/xml/Leads/getAllRecords">
<result><Leads>
<row no="1"><fieldlabel value="LEADID">1111111111</fieldlabel>
<fieldlabel value="SMOWNERID">222222222</fieldlabel>
<fieldlabel value="Lead Owner">soori</fieldlabel>
<fieldlabel value="Company">NiveSoft</fieldlabel>
<fieldlabel value="First Name">Mutha</fieldlabel>
<fieldlabel value="Last Name">Raja</fieldlabel>
<fieldlabel value="Designation">null</fieldlabel>
<fieldlabel value="Email">null</fieldlabel>
<fieldlabel value="Phone">3434343</fieldlabel>
<fieldlabel value="Fax">null</fieldlabel>
<fieldlabel value="Mobile">null</fieldlabel>
<fieldlabel value="Website">null</fieldlabel>
<fieldlabel value="Lead Source">null</fieldlabel>
<fieldlabel value="Lead Status">null</fieldlabel>
<fieldlabel value="Industry">null</fieldlabel>
<fieldlabel value="No of Employees">0</fieldlabel>
<fieldlabel value="Annual Revenue">0.0</fieldlabel>
<fieldlabel value="Rating">null</fieldlabel>
<fieldlabel value="CAMPAIGNID">null</fieldlabel>
<fieldlabel value="Campaign Source">null</fieldlabel>
<fieldlabel value="SMCREATORID">22222222</fieldlabel>
<fieldlabel value="Created By">jkbmahesh</fieldlabel>
<fieldlabel value="MODIFIEDBY">22222222</fieldlabel>
<fieldlabel value="Modified By">jkbmahesh</fieldlabel>
<fieldlabel value="Created Time">2009-02-22 18:20:38</fieldlabel>
<fieldlabel value="Modified Time">2009-10-05 16:01:32</fieldlabel>
<fieldlabel value="Street">null</fieldlabel>
<fieldlabel value="City">null</fieldlabel>
<fieldlabel value="State">null</fieldlabel>
<fieldlabel value="Zip Code">null</fieldlabel>
<fieldlabel value="Country">null</fieldlabel>
<fieldlabel value="Description">null</fieldlabel>
<fieldlabel value="Skype ID">null</fieldlabel>
<fieldlabel value="Email Opt Out">false</fieldlabel>
<fieldlabel value="Salutation">null</fieldlabel>
<fieldlabel value="rrr">null</fieldlabel>
<fieldlabel value="int field">null</fieldlabel>
<fieldlabel value="Currency (Round Up)">null</fieldlabel>
<fieldlabel value="Auto Num">1</fieldlabel></row></result>
<row no="2">
...
</row>
</Leads>
</response>
New format:
- <response uri="/crm/private/xml/Leads/getAllRecords">
<result>
<Leads>
<row no="1">
<FL val="LEADID">1111111111</FL>
<FL val="SMOWNERID">1111122222</FL>
<FL val="Lead Owner">soori</FL>
<FL val="Company">NiveSoft</FL>
<FL val="First Name">Mutha</FL>
<FL val="Last Name">Raja</FL>
<FL val="Email"></FL>
<FL val="Phone">3434343</FL>
<FL val="No of Employees">0</FL>
<FL val="Annual Revenue">0.0</FL>
<FL val="SMCREATORID">22222222</FL>
<FL val="Created By">jkbmahesh</FL>
<FL val="MODIFIEDBY">22222222</FL>
<FL val="Modified By">jkbmahesh</FL>
<FL val="Created Time">2009-02-22 18:20:38</FL>
<FL val="Modified Time">2009-10-05 16:01:32</FL>
<FL val="Email Opt Out">false</FL>
<FL val="Auto Num">1</FL>
</row>
<row no="2">
....
</row>
</Leads>
</result>
</response>
Key Points:
- XML tag has been changed from <fieldlable value=""> field value </fieldlable> to <FL val=""> field value <FL>
- You can stop fetching records with "null" values by passing the newFormat=1 in API request. If you want to fetch data for all the fields (including null values), use the newFormat=2 parameter.
New Response Format - Available from Oct 22, 2009 EOL of Old Response Format - Dec 07, 2009 |
3. No. of API Requests
For a better performance and developer service, we will be limiting the number of API requests as given below:
| Zoho CRM Edition | API Requests - Upper Limit |
| Free Edition (3 users free) | 250 calls / day / organization |
| Professional Edition (USD 12 / user /month) | 250 calls/day / user license OR 5,000 calls /day /organization, whichever is lower |
| Enterprise Edition (USD 25 / user /month) | 250 /day/ user license OR 15,000 calls/day /organization, whichever is lower |
For example, in Free Edition, if you are using the getSearchRecords method, you can fetch a maximum of 200 records per request, in turn, a total of 50,000 records per day (250 x 200 = 50,000 records).
Please note that if you are using the getSearchRecords or getCVRecords methods, you can send a maximum of 250 calls per day irrespective of your Zoho CRM edition.
Important Note:
The above restrictions are applicable for all our existing and new users. In future, we are planning to notify the CRM administrator (Primary Contact of the Zoho CRM account) if your organization exceeds the above mentioned limit. In addition, we will also provide API Statistics for better assessment of your integration requirements.
Implementation Date: Dec 07, 2009 |
From Dec 07, 2009 (12.00 AM PST), you can request API calls as per your Zoho CRM Edition. In case, your application requires more than upper limit, your additional API requests will not be processed. To avoid data transfer issues, please assess your API requirements well in advance. If you need any help, please contact our Support at support@zohocrm.com or call us:+1 888 900 9646.
4. New API Methods
We are really excited to introduce the following new methods for the benefit of growing developer community:
- getSearchRecords
- getSearchRecordsByPDC
- deleteRecords
- convertLead
| API Method | Purpose |
| getSearchRecords | To fetch all users data specified in the API request. |
| getSearchRecordsByPDC | To search the values based on the default pre-defined columns of Zoho CRM entities. |
| deleteRecords | To delete a record by passing its ID. |
| convertLead | To convert lead to account, contact and potential. |
We are confident, the above methods will be very useful in implementation of search functions and allows you to develop additional business logic through our API. These methods will be made available for all editions immediately.
Available From: Oct 22, 2009 |
5. Other Changes
In addition, we are incorporating the following minor changes:
- Fetch a maximum of 200 records per API request
- New Response format is applicable to all API methods (existing as well as new methods)
- Fetch records with the specified fields using the selectColumns parameter.
- We have also updated API Guide and launched official Developer Forums .
Thank you in advance for your kind cooperation.
Best Regards,
Gopal
(Team Zoho CRM)
UPDATE on Nov 26, 2009:
Extended End of Life Date for another 45 days - from Dec 07, 2009 to Jan 21, 2010. Now the total duration is 90 days.
Published On: Oct 22, 2009
Last Updated On: Nov 26, 2009
Last Updated On: Nov 26, 2009
Replies(36)
Re: Zoho CRM API Update - Important
2 years ago
Gopal -- thanks for the detailed explanation ... very exciting stuff.
some follow up questions:
#1 your announcement above say 250 calls per day for getSearchRecords, but the wiki page says 50. which value is correct?
#2 under topic 2. New Response Format above, you mention the shorter structure of <FL val=> ... will that also apply to the xmlData that we send in for methods such as insertRecords adn updateRecords?
#3 also from topic 2. New Response Format, what will happen in December when the new format becomes standard with respect to nulls? will the default behavior be to exclude nulls (option1) or include nulls (option2).
#4 with respect to the getSearchRecordsByPDC method, can you clarify the maximum number of calls per day (if any).
cheers,
-e
Leave a comment on tongerdev's reply
Re: Zoho CRM API Update - Important
2 years ago
Since this rollout, i've been unable to use the Creator API - I simply receive blank responses.. Is anyone else having similar issues?
Re: Zoho CRM API Update - Important
2 years ago
do you mean insertRecords? ours continue with no issues...inserts, updates, and deletes all firing nicely.
cheers,
-e
cheers,
-e
Leave a comment on wiredliving's reply
Re: Zoho CRM API Update - Important
2 years ago
Hey e,
No using Zoho Creator API gives me no results - no matter which query type (xml & csv) it started happening about the same time this CRM API Update was pushed live - so just seeing if anyone else has this issue.
Re: Zoho CRM API Update - Important
2 years ago
Dear wiredliving,
Sorry for the inconvenience.
Currently, our CRM API update doesn't contain any Zoho Creator related changes.
It will be very helpful for us, if you could post the exact issue in Zoho Creator forum.
http://forums.zoho.com/zoho-creator/application-development
I will ask my Creator team to post their comments. Please bear with me in the meantime.
Best Regards,
Gopal
Re: Zoho CRM API Update - Important
2 years ago
Dear wiredliving,
We have replied for this here at http://forums.zoho.com/#Topic/2266000000634122
Sathya, ZohoCreator Team.
Leave a comment on wiredliving's reply
Re: Zoho CRM API Update - Important
2 years ago
Hello!
First, thank you for your kind words.
Please see my answers below:
Gopal: I updated Wiki page with max. 250 calls per day. This is applicable only for the getSearchRecords method. #1 your announcement above say 250 calls per day for getSearchRecords, but the wiki page says 50. which value is correct?
Gopal: The new XML response format is applicable to all methods - insert, update, convert and search functions. #2
under topic 2. New Response Format above, you mention the shorter
structure of <FL val=> ... will that also apply to the xmlData
that we send in for methods such as insertRecords adn updateRecords?
Gopal: After Dec 07, 2009, by default we will exclude the null values in response, i.e, newFormat=1 is applied by default even you are not passing this additional parameter. #3
also from topic 2. New Response Format, what will happen in December
when the new format becomes standard with respect to nulls? will the
default behavior be to exclude nulls (option1) or include nulls
(option2). #4 with respect to the getSearchRecordsByPDC method, can you clarify the maximum number of calls per day (if any).
Gopal: 250 call/day restriction will be applied only to the getSearchRecords method. You can use the getSearchRecordsByPDC like other methods - No of calls as per your Zoho CRM edition.
Please keep posting your suggestions and comments. Your feedback will definitely help us to provide a better API in future.
Gopal
Re: Zoho CRM API Update - Important
2 years ago
This is absolutely ridiculous on the API development team! First, WHY DIDN'T YOU PUT IT IN YOUR ORIGINAL API WIKI DOCS THAT YOU WERE GOING DEPRECATE A METHOD and the bloody field values SOON. This should have been in the docs many months prior to this announcement!
And giving a 1 & 1/2 months for everyone to roll over there code to the new methods and xpaths is a ridiculous amount of time.
This is a complete disregard to your development community! JUST LET US KNOW WHAT'S GOING TO HAPPEN. WE DON'T HAVE A CRYSTAL BALL! You just wasted sooooo much of my time!
Please consider supporting these methods a little longer. Consider the fact that I will now have to spend many FREE NON-BILLABLE HOURS FIXING MY CLIENTS APPLICATIONS. This could have been avoided simply by putting off the project a month until the API had been updated.
On the flip side, I really do like the new methods and I do agree the changes are needed, but YOU JUST NEED TO BE MORE UPFRONT!!!!!
Re: Zoho CRM API Update - Important
2 years ago
Gopal & Zoho Team,
need some more clarification ... we have over 20 user licenses on the Enterprise package ... we fire most/all of our API calls as the master / root-user ... your original post says:
am i
reading this correctly to say that we only get 250 API calls / day? 250 /day/ user license OR
15,000 calls/day /organization, whichever is lower
or
is it 250 * 20users = 5000?
furthermore, are you saying that if a client exceeds the max number of calls per day, that's it??? is there no "buy X more calls @ Y$" add-on? it's understandable that bandwidth may be an issue, but imposing hard limits without any other option is just ridiculous (or some other more appropriate word that would get banned if i type it).
-e
Leave a comment on gopal's reply
Re: Zoho CRM API Update - Important
2 years ago
@tongerdev:
Since you have 20+ Enterprise Edition licenses, by default your Zoho CRM account will get 250 x 20 = 5000 API calls/day for your organization.
Are you saying that if a client exceeds the max
number of calls per day, that's it??? is there no "buy X more calls @
Y$" add-on? it's understandable that bandwidth may be an issue, but
imposing hard limits without any other option is just ridiculous (or
some other more appropriate word that would get banned if i type it).
I just want to assure you that, we don't want to impose any hard limits on our valuable API users like you. We want many more developers to embrace our API and integrate with third-party apps in a mutually beneficial way. On need basis we are happy to enable additional API calls upon request. We will review the request before enabling additional API calls with or without additional amount. As mentioned in my announcement, please let us know your API needs at support at zohocrm dot com or call us + 888 900 9646
@srhyne
Firstly, thank you for using our API extensively for your clients and taking time to post your feedback.
We will definitely consider your suggestion in our future API updates. WHY DIDN'T YOU PUT IT IN YOUR ORIGINAL API WIKI DOCS THAT YOU WERE
GOING DEPRECATE A METHOD and the bloody field values SOON. This should
have been in the docs many months prior to this announcement!
Based on our current API stats, we assessed 45 days is sufficient to port the existing methods and response format to new one. However, based on our users' feedback, we will be glad to review the situation and make necessary amendments to our announcement. In the meantime, please bear with me. Please consider supporting these methods a little longer. Consider the
fact that I will now have to spend many FREE NON-BILLABLE HOURS FIXING
MY CLIENTS APPLICATIONS. This could have been avoided simply by putting
off the project a month until the API had been updated.
Thank you for your appreciation and constructive feedback :) On the flip side, I really do like the new methods and I do agree the
changes are needed, but YOU JUST NEED TO BE MORE UPFRONT!!!!!
@Developers
Thanks again for reading my replies. Please don't hesitate to post your suggestions and comments - good or bad. We really appreciate your feedback and take the necessary steps in future.
Best Regards,
Gopal
Re: Zoho CRM API Update - Important
2 years ago
Gopal,
thanks again for the clarification 
cheers,
-e
Leave a comment on gopal's reply
Re: Zoho CRM API Update - Important
2 years ago
I am trying to use insertRecords API using new <FL val="something"></FL>, xmlData, but it is not inserting any record, and i am getting error as "<error><code>4500</code><message>Problem occured while processing the request</message></error>" in response.
Am i doing something wrong?
Re: Zoho CRM API Update - Important
2 years ago
are you passing newFormat=1 or newFormat=2 in your API call?
point #2 in the original post says:
cheers, Till Dec 7, 2009, by default,
you will get the response in the old format. If you want to get the
response in the new format, you must pass the extra argument with newFormat=1 or 2 in API request.
-e
Leave a comment on test.inmobi's reply
Re: Zoho CRM API Update - Important
2 years ago
I agree that the notice was very short, especially since I just heard about it today via email - I don't follow the forum. Maybe I missed a prior email, but I agree 45 days to change things is very short time. I outsource all work, so I have to get in touch with the programmer and hope he can do the work, we can test it and go live, all while trying to do do businessm not to mention a major holiday.
More notice and earlier notice would have been nice, this really has put me in a bind to get done in only 2 weeks!
Leave a comment on steve_ami's reply
Re: Zoho CRM API Update - Important
2 years ago
@test.inmobi & @tongerdev - re the insertRecords API call - I was getting the error message below with newFormat=2 as I wasn't passing in all of the field names as some of them were null. I altered the url to have newFormat=1 and it worked fine and I still don't have to define all of the null fields.
Error Message I was getting:
<?xml version="1.0" encoding="UTF-8" ?>
<response uri="/crm/private/xml/Cases/insertRecords"><error><code>4500</code><message>Problem occured while processing the request</message></error></response>
Note: this post was just to make it easier for the next person with this issue :)
Error Message I was getting:
<?xml version="1.0" encoding="UTF-8" ?>
<response uri="/crm/private/xml/Cases/insertRecords"><error><code>4500</code><message>Problem occured while processing the request</message></error></response>
Note: this post was just to make it easier for the next person with this issue :)
Leave a comment on collings.simon's reply
Re: Zoho CRM API Update - Important
2 years ago
Also to make it easier for people these are the changes that I've made to implement these API alterations (basically to get you to the point you are at pre-change):
P.S. I like the new APIs - well done. I hope you are going to look at the incoming requests in early December and contact people know if they are still using the old API calls.
- Alter <fieldlabel value="Something">Anything</fieldlabel> to <FL val="Something">Anything</FL> - i.e. change 'fieldlabel' to 'FL' and 'value' to 'val'
- In my calling URL add the parameter newFormat=2 for any get information requests - i.e. will return all the null fields so you won't get any exceptions for missing XML nodes
- In my calling URL add the parameter newFormat=1 for any insert information requests - i.e. don't have to specify all the null fields
P.S. I like the new APIs - well done. I hope you are going to look at the incoming requests in early December and contact people know if they are still using the old API calls.
Leave a comment on collings.simon's reply
Re: Zoho CRM API Update - Important
2 years ago
Hello!
Thank you for sharing your valuable suggestions and comments on our API update.
Now, I am very happy to inform you all that we are extending the End of Life date from Dec 7th, 2009 to Jan 21st, 2010
Please keep posting your valuable suggestions and comments.
Best Regards,
Gopal
Leave a comment on gopal's reply
Re: Zoho CRM API Update - Important
2 years ago
Gopal,
It would be very useful to have an additional information returned back from the API, both indicating the amount of requests left, and a unique error code in order to let handle the error in an appropriate way.
By the way, at what timezone and hour the API counter is resetted?
Thanks,
Guido
Leave a comment on guido.mazzanti's reply
Re: Zoho CRM API Update - Important
2 years ago
Dear Guido,
We will definitely analyze regarding the provision of API count in the response. Currently, you can see the API usage statistics in the Zoho CRM Setup page (Setup -> Admin Settings -> Developer API Key). Also once the api count exceeds, we will throw a error with proper error code. We will let you know the error message and code details soon. After that, you can use that error code to handle the limit exceed error. Hope this clarifies.
Regards,
Mahesh,
(Zoho CRM Team).
Re: Zoho CRM API Update - Important
2 years ago
so ... as we are now 3 days from the cutover/end-of-life ... please provide an update on whether this is a go or not.
i have opened several tickets which have not been resolved (see below) ... the first one is clearly a show-stopper for us (inserting Quote/Invoice with Product Details fails when using newFormat=1):
http://forums.zoho.com/#Topic/2266000000766017 - insert Product Details to Quote/Invoice with newFormat=1 fails
http://forums.zoho.com/#Topic/2266000000626377 - set text field to null/empty
http://forums.zoho.com/#Topic/2266000000715376 - update Product Details in Quotehttp://forums.zoho.com/#Topic/2266000000652298 - API call to empty recycle bin
just curious to know what the official ZohoCRM team plans are for this week.
cheers,
-e
Leave a comment on maheshkumar's reply
Re: Zoho CRM API Update - Important
2 years ago
@ tongerdev,
We have fixed 1st and 3rd ticket in the local setup. We will update that in the site soon and let you know. We will give considerable amount of time before the main release to change the implementation accordingly. You can change your implementation within that time frame.
Regarding the 2nd ticket, we are working on it. We will provide the option soon.Regarding the 4th ticket, we will start working on it soon. kindly bear with us.
@ Guido
We will throw the error code "4421", when the API call exceeds your limit. You can use this error code to handle it in your code.
Regards,
Mahesh,
(Zoho CRM Team).
Leave a comment on maheshkumar's reply
Re: Zoho CRM API Update - Important
2 years ago
Mahesh -
You explained:We will give considerable amount of time before the main release to
change the implementation accordingly. You can change your
implementation within that time frame.
Question -- What is "that time frame"? Since we are less than three days from the announced date, and such could not be considered a "considerable amount of time", does this mean that the January 21st date has indeed been postponed? What is the new date?
Thanks,
David
Leave a comment on ihmtcontact's reply
Re: Zoho CRM API Update - Important
2 years ago
Dear David,
We will update the mentioned issues in the site probably by coming Thursday. After that, we will give another 10 days time to change your implementation accordingly. But, no of API calls restriction will get implemented as announced (by January 21) . We are giving 10 days time frame for changing your response and request format based on new format. In that time frame, both old and new format will work only for the mentioned issues.
Regards,
Mahesh,
(Zoho CRM Team).
Leave a comment on maheshkumar's reply
Re: Zoho CRM API Update - Important
2 years ago
just to recap this and make sure there are as few surprises as possible:
- on 21 JAN, we should expect Product Details issues (insert fails for newFormat=1 and updates fail for to price/qty/etc) to be resolved ...
- on 21 JAN, the deprecated methods will not longer work ...
- on 21 JAN, the number of API calls will be restricted/limited as specified above ...
- from 21 JAN to 01 FEB, we will still have to specify newFormat=1 or newFormat=2 to use the <FL val=> ... and ... if nothing is specified, the old format of <fieldlabel value=> will be assumed ...
- on 01 FEB, the "default" will be newFormat=1, so unless we want to include the nulls (newFormat=2) in the response, we no longer need to specify newFormat=1 ...
is that correct? or am i missing something?
cheers,
-e
Leave a comment on tongerdev's reply
Re: Zoho CRM API Update - Important
2 years ago
Dear tonderdev,
Yes, you are correct. From JAN 21 to FEB 1, you have to use newFormat parameter to get the new response format ("<FL") and if nothing is specified, you will get the old format.
From FEB 1 onwards, by default you will get the response in new format (without null values).
In JAN 21 update, following things will get updated.
1. Fix for the issues regarding insert/updateRecords for newFormat parameter.
2. No of API calls restriction.
3. Deprecation of search methods.
Hope this clarifies.
Regards,
Mahesh,
(Zoho CRM Team).
Leave a comment on maheshkumar's reply
Re: Zoho CRM API Update - Important
2 years ago
Hello, I am new to developing to this API. Glad to get in now. :-)
I have crafted my insertRecords request, and the response is
4500 Problem occured while processing the request
I am using the NewFormat=1 parameter, and as far as I can tell, everything looks good. Could you kindly suggest a means of troubleshooting this vague error message? Thank you!
Some things not especially clear in the documentation:
I have crafted my insertRecords request, and the response is
4500 Problem occured while processing the request
I am using the NewFormat=1 parameter, and as far as I can tell, everything looks good. Could you kindly suggest a means of troubleshooting this vague error message? Thank you!
Some things not especially clear in the documentation:
- Which fields are required when inserting a Lead?
- Is there a special way to insert to a bound field (listbox) -- I'm just sending the literal value in normal FL field, is this correct?
- If I need to insert a blank value, how is that accomplished?
- Is there debugging I might enable or a log I might access via the CRM interface or elsewhere to get more details on the error?
Leave a comment on chuckyb's reply
Re: Zoho CRM API Update - Important
2 years ago
Dear Chuckyb,
You have given NewFormat=1. This is reason for the error. It should be "newFormat=1".Kindly correct this.
Regards,
Senthamil Bharathi.S
[Zoho CRM Team]
You have given NewFormat=1. This is reason for the error. It should be "newFormat=1".Kindly correct this.
- To insert Leads, You can give default fields as well as custom fields.
- We have listed some samples in our API wiki help. Refer here
- Simply leave that field while insert the record.Or you can give as <FL val="fieldName"></FL>
- We are enhancing our error codes and log details.
Regards,
Senthamil Bharathi.S
[Zoho CRM Team]
Re: Zoho CRM API Update - Important
2 years ago
While I wrote it as NewFormat in this message, the request parameter is correctly newFormat=1.
Do you expect to implement more verbose error messages anytime soon? Thanks.
Do you expect to implement more verbose error messages anytime soon? Thanks.
Leave a comment on Senthamil Bharathi's reply
Re: Zoho CRM API Update - Important
2 years ago
Dear Chuckyb,
Sorry about that.We are working to remove this kind of verbose error mistake.In future we will handle this in proper way and we will make all param in lower case.
Regards,
Senthamil Bharathi.S
[Zoho CRM Team]
Re: Zoho CRM API Update - Important
2 years ago
I just wish after 8 working days I would just like it if someone from Zoho would actually call me back.
If you all don't contact me and fix our technical issues today I am giving my business to Sales Force Friday morning....
Upset,
Brad Boruk
National Credit Solutions
Owner & Credit Strategist
214-504-7101 Direct
b.boruk@ncs700.com
If you all don't contact me and fix our technical issues today I am giving my business to Sales Force Friday morning....
Upset,
Brad Boruk
National Credit Solutions
Owner & Credit Strategist
214-504-7101 Direct
b.boruk@ncs700.com
Leave a comment on Senthamil Bharathi's reply
Re: Zoho CRM API Update - Important
2 years ago
Hello, I am now attempting to insert your Sample Lead XMLDATA from http://zohocrmapi.wiki.zoho.com/insertRecords-Method.html and still getting a 4500 error. I tried changing SMOWNERID to a valid user id and that had no effect. I took off the CAMPAIGNID because I don't think we have campaigns set up.
I do have a valid API key and ticket, and I used the same block of code to perform a simple getRecordByID request successfully.
If you have a log that you can look in, you'll see about an hour of unsuccessful requests leading up to the time of this post. If you can see anything and advise, I'd appreciate it.
Please let me know what you think. Thanks again! ~Chuckyb
I do have a valid API key and ticket, and I used the same block of code to perform a simple getRecordByID request successfully.
If you have a log that you can look in, you'll see about an hour of unsuccessful requests leading up to the time of this post. If you can see anything and advise, I'd appreciate it.
Please let me know what you think. Thanks again! ~Chuckyb
Re: Zoho CRM API Update - Important
2 years ago
Hello,
I also would like to add records to a field which is a picklist that supports multiple values. Can you please explain how to format the multiple values? I have not found this documented anywhere. Thank you.
It is taking me a month to complete the very simple task of integrating one little website form into CRM, due to lack of documentation and slow technical support response. It's embarrassing that this task has taken more than an hour, honestly.
SUGGESTION: If you are not going to be attentive to a support forum, shut it down. In this context, I'd define "attentive" as < 24 hour response time.
Are there better support avenues than this forum?
I also would like to add records to a field which is a picklist that supports multiple values. Can you please explain how to format the multiple values? I have not found this documented anywhere. Thank you.
It is taking me a month to complete the very simple task of integrating one little website form into CRM, due to lack of documentation and slow technical support response. It's embarrassing that this task has taken more than an hour, honestly.
SUGGESTION: If you are not going to be attentive to a support forum, shut it down. In this context, I'd define "attentive" as < 24 hour response time.
Are there better support avenues than this forum?
Leave a comment on chuckyb's reply
Re: Zoho CRM API Update - Important
2 years ago
Dear chuckyb,
You can insert value for multi-picklist.You have to give the values separated by semi colons.Kindly have a look at the below example.
&xmlData=<Leads><row no="1"><FL val="Company">Sample</FL>..........................................................<FL val="multipicklist">1stvalue;2ndvalue;3rdvalue</FL>.............................</row></Leads>
Regarding 4500 error code for insertRecords, We are ready help, Kindly mail us your contact details and convenient time to support at zohocrm dot com.We will arrange a Zoho Meeting(Desktop Sharing) to resolve your problem.
Regards,
Senthamil Bharathi.S
[Zoho CRM Team]
Re: Zoho CRM API Update - Important
2 years ago
Chuckyb and Zoho CRM team,
Our team has created a cool Snap (integration) to any SaaS or software out there for Zoho CRM. We will be posting here soon and on the SnapLogic.com developer board similar issues around integration to Zoho CRM and other cool Zoho solutions our members are requiring.
Feel free to email me anytime,
Clint
Our team has created a cool Snap (integration) to any SaaS or software out there for Zoho CRM. We will be posting here soon and on the SnapLogic.com developer board similar issues around integration to Zoho CRM and other cool Zoho solutions our members are requiring.
Feel free to email me anytime,
Clint
Re: Zoho CRM API Update - Important
1 year ago
Hello,
When i am trying ot insert Lead record using API getting below error.
There is no specification what this specific error is. i have worked on about 7 to 8 different API's but ZOHO is having very poor support and dont have good document.
can anyone please help me in this error.
Regards,
kiran
When i am trying ot insert Lead record using API getting below error.
4500Problem occured while processing the requestThere is no specification what this specific error is. i have worked on about 7 to 8 different API's but ZOHO is having very poor support and dont have good document.
can anyone please help me in this error.
Regards,
kiran
Leave a comment on Senthamil Bharathi's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic
Reply to gopal's announcement
{"z4252270":[2266000001731318],"z1981313":[2266000000636416],"z455849":[2266000000834330,2266000000857272,2266000000871638,2266000000874146],"z2010391":[2266000000635122,2266000000635152,2266000000636468,2266000000634377,2266000000652284,2266000000790023,2266000000798013],"z2516034":[2266000000636627],"z198593":[2266000000787361,2266000000788091,2266000000788458,2266000000800471],"z1220215":[2266000000902417],"z2407976":[2266000000773083,2266000000801219],"z120249":[2266000000634013,2266000000634134,2266000000634132,2266000000636531,2266000000680227],"z1567493":[2266000000871386],"z284197":[2266000000636299],"z1411652":[2266000000673781,2266000000673787],"z288463":[2266000000851410,2266000000866263,2266000000874365],"z2925507":[2266000000789258],"z622020":[2266000000668727],"z984058":[2266000000636201,2266000000634130]}
Statistics
- 36 Replies
- 18971 Views
- 3 Followers
Actions
