support latest Intercom API

[spang]

Hi there,

This doesn't seem to support the latest Intercom API, and instead uses the v1 API. Are there any plans to support the latest API?

http://doc.intercom.io/api/#intercom-api

Some documentation links from the old API docs do not work anymore, and new features are only available with the new API.

Thanks for writing these Python bindings!

[flc]

There is an apiv2 branch, might worth a try. Works for me so far but I only tried basic stuff, like managing users.
@jkeyes how stable would you consider the code in the apiv2 branch?

[nerdburn]

Ping! Very interested in this as well.

[Madd]

How is the development going for v2?

[jkeyes]

The truth of the matter is that I've had no time to dedicate to this for a while now. I'm not sure what state the v2 API is in. FWIR it was supporting the majority of the features from the v1 API. I don't know how stable it is as I haven't compared to the latest API docs. Sorry I can't be clearer about this.

[greenafrican]

Chatted to Intercom today and they don't have any plans to release a Python client anytime soon so will be great to bring this fantastic project inline with the v2 API. Thanks for the work to date.

[flc]

I got the same response from them about a month ago: "... we've no immediate plans to add more client libraries at the minute ...". I'm using the apiv2 branch of my fork in production. No problem with it so far, but I'm only using a few endpoints: users, events, conversations/messages.

[jkeyes]

I'm reviewing the branch now. My gut tells me it's in pretty good shape. I just need to verify that. I'm currently comparing features against the official Ruby library.

[jkeyes]

BTW folks, any help is welcome.

[jkeyes]

I compared the tests from intercom-ruby with python-intercom and I think there is only one big difference between the two and that's error handling support. I'll start work on this next and then review the open issues.

[flc]

I needed to make some changes/fixes in my fork, you can take a look at them and decide whether you want to apply them. Because of your recent changes there are some merge conflicts now: apiv2...flc:apiv2

[flc]

Also, how can I run the tests? It would probably worth a mention in the readme or somewhere. Thanks

[flc]

ah, ok, sorry, it's here: http://python-intercom.readthedocs.org/en/latest/development.html#running-the-tests. I was misled a bit by this: https://github.com/jkeyes/python-intercom/blob/apiv2/dev-requirements.txt

I get a lot of

from intercom import HttpError
ImportError: cannot import name HttpError

[jkeyes]

apiv2 is using describe for running the unit tests. I'll add it to the README. The docs are out of date as they are for v1 of the API.

[jkeyes]

@greenafrican (I got your comment via email but no sign in the Github UI) I'm hoping to fix the structure so you can do from intercom import User style imports. I don't think you should do any documentation updates until I've confirmed that, as it might just be a waste of your time.

There is no change to all, for example: https://github.com/jkeyes/python-intercom/blob/apiv2/tests/unit/collection_proxy_spec.py#L29

[jkeyes]

@flc I've applied some of your changes to the apiv2 branch. Thanks.