-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ResourceNotFound error #44
Comments
👍 |
@skunkwerk @snario Have you tried this with the latest code on the apiv2 branch? (Sorry for being so very late in replying) |
@skunkwerk @snario Version 2.0.alpha has been released: https://pypi.python.org/pypi/python-intercom/2.0.alpha Let me know if you still encounter the problem. |
Hi @jkeyes I'm using the newly merged master and am receiving this error. |
Hey @greenafrican. Please include some example code that reproduces the problem, and I'll take a look. |
Pretty basic:
|
@greenafrican If |
A |
Yeah. The 404 status code indicates that what was requested could not be found. In the case of this call what is being requested is an See the API docs for the full list of HTTP status codes returned by the API: https://doc.intercom.io/api/#http-responses |
Ok cool. I thought
;) Thanks for the stellar work! |
Hi John,
thanks for putting together this library for our use.
Do you know what this error means? I try the same call from my console, and I don't get any error - so I'm not sure what's causing this.
File "/src/index.py", line 399, in send_event_to_intercom
impression = Event.create(event_name=event, user_id=customer_id, metadata=properties)
File "intercom/events.py", line 17, in create
resp = Intercom.create_event(event_name=event_name, user_id=user_id, email=email, metadata=metadata)
File "intercom/intercom.py", line 463, in create_event
'POST', Intercom.api_endpoint + 'events', params=params)
File "intercom/intercom.py", line 66, in wrapper
raise_errors_on_failure(response)
File "intercom/intercom.py", line 76, in raise_errors_on_failure
raise ResourceNotFound("Not found.")
The text was updated successfully, but these errors were encountered: