The requested resource does not exist; check your path and try again

Intercom::ResourceNotFound • Events::UpdateIntercomLeadWorker@default

The requested resource does not exist; check your path and try again
I am going to save the contacts like this in rails:
i got he above error 

def find_lead(lead_id)


@intercom.contacts.find(id: lead_id)

rescue Intercom::ResourceNotFound

return nil



second one issue I am also facing this issue
@intercom.contacts.find(id: lead_id)
12:59:09 worker_sidekiq.| *** Intercom::UnexpectedError Exception: The error of type '' is not recognized. It occurred with the message: Your current SDK version is incompatible with version 2.10 of the API and http_code: '400'. Please contact Intercom with these details.


Best answer by mateusz.leszkiewicz 7 May 2024, 14:34

View original

5 replies

Userlevel 2
Badge +4

Hi jahanzaib, It’s Mat from the Support Engineering Team 😀

It looks like your SDK is outdated. Can you please update SDK of your app to the latest version and check if that will do the trick?

hi @mateusz.leszkiewicz can you please help me how we can update the SDK of my app.Regards

Userlevel 2
Badge +4

Sure, which SDK are you using? React, iOS, Android?

You can find suitable instructions in our developer documents here.

Hi there, we are using the unofficial python SDK hosted on your Github and have started encountering this problem since 30 April 2024.


The API version we are using is 1.4 which is quite old but the library above does not support newer versions.


The error we are seeing occurs as follows:


  1. We search for a lead using an email address
  2. If we find a result in step 1 we fetch that lead using the SDK and the ID from above. The SDK issues a GET request to<id-of-contact> which returns data and a 200 status code.
  3. Using the lead from step 2 we update the lead with new data using the SDK. This issues a PUT request to<id-of-contact> which fails with a 404 status code.

Can you confirm if there is anything that has changed in the intercom API?

Userlevel 2
Badge +4

Hi BradleyK

This is very outdated SDK (6 years since the last commit) and as stated in the Readme file, it is not officially supported anymore.

From what you’ve described, the issue might be appearing due to the fact that it uses outdated API version (current version is 2.11).

I would start looking for an answer to your question there. 😎