Hello Dear Intercom-Support-Team, as of recently we noticed a strange behavior in our application and it is no longer possible to start a conversation programmatically from our application. The server returns 400 http error on request.We have not changed anything in the intercom settings (I have asked the entire support team) SDK Keys are not expired or so, and have been never changed. Other functions of Intercom Messenger are not affected.Could You please help here, as we use this functionality to provide our customers the possibility to send us Device Logs.Mobile Platforms affected: iOS, Android (both native Apps)Intercom SDK Version: 15.5.0 (also tested with 15.6.2 the same behaviour) POST https://jabaugui-android.mobile-messenger.intercom.com/messenger/mobile/conversationsRequest:{ "body" : "App: lexoffice Android, Version 267 ….", "from" : { "id" : "{id here}", "type" : "user" }, "app_id" : "{app id here}", "hmac" : "{hmac string here}", "user" : { "email" : "{my email here}", "type" : "user", "user_id" : "{user id here}" }}Response: 400 POST https://jabaugui-android.mobile-messenger.intercom.com/messenger/mobile/conversationscache-control:no-cachecontent-encoding:gzipcontent-type:application/json; charset=utf-8date:Fri, 16 Feb 2024 12:22:19 GMTserver:nginxstatus:400 Bad Requeststrict-transport-security:max-age=31536000vary:Accept,Accept-Encodingx-intercom-version:ae8c66d841ff238ea75264a694cb18faa958b982x-request-id:0000dl33g36r9ir9u7kgx-request-queueing:0x-runtime:0.068291�??{S�e??�Q�0D��Pګ��]b01qwS(�w7u~߼�l��H�S�j0��s%�el�w蝿�0�6x:&*f6�9~L] �*��^��{Z]�j*H�Da��???????��??�Ί??????

Hi Mateusz,in the initial post I mentioned all the details, in the response header you can findthe request id.I also tried to make a request with the Bearer Authentication with Access Token to (https://api-iam.eu.intercom.io) as mentioned in the documentation but also unsuccessful - there I receive http error 401.https://developers.intercom.com/docs/references/rest-api/api.intercom.io/Conversations/createConversation/Hey there @Artiom C!I can see that my teammate Eden is helping you out with your mobile API question in a Support conversation. I’ll let her continue to help you out on that one. Regarding our REST API which you referenced above, I should note that the URL that the URL that you mentioned above is incorrect. You should be usinghttps://api.intercom.io/{insert endpoint}. EU URLs are only for workspaces that have their data hosted in the EU. So if you are based in the EU, but have your data hosted in the U.S. you would usehttps://api.intercom.io(also note that it’s simply “api”, not “api-iam”.Hope that helps with part of your issue at least!

Hi Artion,I can see that, but we have access only to the logs that are no older than 7 days, and it might be easier to track the issue if you start a conversation in Messenger with us. We will definitely need you to recreate the issue one more time to see what’s going on and document it properly.Can you do that please?

Start a conversation programatically stopped working

Start a conversation programatically stopped working | Community

Join the Intercom Community 🎉

Intercom Customers and Employees

Login to the community

Intercom Customers and Employees

Scanning file for viruses.

This file cannot be downloaded