Conversation not created when the parameter In_reply_to_status_id is being used

[TestChrysalis]

Hello, we have a case in which we created a tweet from the call: https://api.twitter.com/1.1/statuses/update.json?status=%40svinuesa%20Hola%2C%20siento%20lo%20tu%20malestar%2C%20voy%20a%20revisar%20lo%20que%20me%20indicas%20para%20tratar%20de%20darte%20respuesta%20cuanto%20antes.%20Si%20te%20puedo%20ayudar%20en%20algo%20mientras%20lo%20gestiono%2C%20quedo%20a%20tu%20disposición%20por%20DM.%20Un%20saludo.&In_reply_to_status_id=1055538800296898564&auto_populate_reply_metadata=false

and yet a conversation has not been created on Twitter and it does not appear that the tweet https://twitter.com/svinuesa/status/1055538800296898564 has an answer, when it should have it.

What can be happening?

Thank you.

[hmz]

Hi @TestChrysalis. Requests parameters are case sensitive.

The problem is likely due to the capital I at the start of the parameter: In_reply_to_status_id

Try replacing it with the following to see if it works: in_reply_to_status_id

Please check out our documentation on the request parameters for the POST statuses/update API.

Hamza

[TestChrysalis]

Sorry, it`s because translation software, i actually using this parameter: in_reply_to_status_id.

Thank you.

[hmz]

Ah, no problem.

My next step would be to try changing auto_populate_reply_metadata=false to auto_populate_reply_metadata=true . Let me know how that goes.

Hamza

[system]

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.