Replying to a V2 message with the V3 API creates a new thread

Question and Answers
,
1

Hi,

We are currently in the process of migrating from the Nylas V2 to V3 API. We are currently grouping messages by thread ID and are encountering an issue where we are unable to reply to a V2 message with the V3 API (reply_to_message_id ). As a result it is creating a new thread.

As a solution we were thinking of adding a custom header with the V2 thread ID when sending using the V3 API and then mapping back when receiving the message webhook but it turns out custom headers are not sent back.

TLDR, there are 2 questions here:

  • How do we reply to a V2 message ID with the V3 API and retain the original thread ID to have a smooth migration for our users
  • If not possible, what would be the best approach to resolve this?

Thank you,

Vincent

2

hi @vincentg, this sounds like it could be a bug. Can you please submit a support ticket through the dev portal with more information on what you are encountering?

3

Hi Spang,

Which part would be a bug? Creating a new thread ID on reply or not receiving custom headers in webhooks?

Thanks,

Vincent

4

Creating a new thread ID on reply