It was a nightmare working with this. The documentation was horrible and then having API calls that are avaiable with abousolutely no documentation was unreal... I honestly couldnt believe it - coming from an established CRM company - this is completely unacceptable.
And the task that we were trying to perform was a very common one, it shouldn't have been such a task to get it to work.
I like the CRM - in most other aspects it was very good - but the API and it's related support needs much work. You cannot have undocumented API calls, its unacceptable. That makes the API call completely useless. And asking a developer to completely guess at (several!!) open-text parameter values is completely unacceptable, as our chances of guessing the correct values that your system is expecting is almost 0%. If you have a parameter that is expecting a certain value - you MUST LIST ALL VALUES THAT PARAMETER IS EXPECTING IN THE DOCUMENTATION - you cannot tell the developer to just guess!!! Thats insane!!
I will never take a job that deals with the methodCRM API again - it was a complete nightmare. My best wishes to any other developers who venture to work with this api... good luck!
PS - You cannot try to charge companies for support of your API when your documentation is incompleted and call it extra development work. It's not extra - its just making up for the fact that you were lazy in the first place and didnt document your API correctly, and then when a developer needs to use said API calls, you cannot then charge them for asking questions because there is no documentation. Thats a great way to lose customers and developers.
I hope you guys change this problem quickly - because otherwise your system was very good. I liked working with it other than the API. If you cannot document it correctly - then kill it until you can. Because otherwise your just hurting yourselves.
Best of luck!