V2 Api changes

[dammitjanet]

What are you plans to support the new (March 2016) v2 API with higher rate limits?

[jjb3rd]

I didn't know there was a new api. I'd be happy to merge pull requests that work with the new api if you fee like putting in the work.

[dammitjanet]

I've already started looking into the upgrade and forked the repo as I prefer the process model you've implemented over the other Freshdesk (SN) package.

With respect the the changes... a lot has changed in both methods and models. Considering the following (emphasis mine), an upgrade to V2 is the best path.

API deprecation and breaking change policies

The existing version of the APIs (v1.0) has been deprecated. There will be no further updates or releases. However, the v1 APIs will continue to be functional until the end of September.

We will also notify you 60 days in advance before a breaking change comes into effect.

It's quite possible that the v1 API is still working, but its very probable that it will be turned off at some point in the very near future.

Looking at the code in its current state, I'd say that the implementation is very young and has a lot of limitations in terms of making this a useful package (for my use case that is)

• GET T methods
• GET List methods
• Create new models for the updated v2 API objects

[Meddington]

Freshdesk just notified that the v1 API is end-of-life in July. Has anyone started patching to v2?

[jjb3rd]

I've stopped working on this due to lack of time. If anyone feels like taking up the mantle, by all means, feel free.

[derekantrican]

I don't think this works anymore without upgrading to API v2: