{"version":"2.1.295","anchor":"sdk-stream-events-gain-api-message-id","canonical_anchor":"sdk-stream-events-gain-api-message-id","heading":"Every SDK stream event now says which reply it belongs to","tier":"use","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/sdk-stream-events-gain-api-message-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Every SDK stream event now says which reply it belongs to\n\nEach SDK stream event between a reply's start and stop now carries an `api_message_id`, so programs can match events to replies\n\n**What**\n\nEvery stream event between the start of a reply (`message_start`) and its end (`message_stop`) now carries an `api_message_id` field naming the reply it belongs to. Before, a program reading the stream had to remember the `message_start` to know which reply later events were part of.\n\nThe field is marked internal, and it is not present in Remote Control sessions.\n\n**Why**\n\nA program that joins a stream partway, or misses a `message_start`, can still tell which reply each event belongs to. Because the field is marked internal, code that relies on it should be ready for it to change.\n\n- Area: SDK\n- Names: `api_message_id`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}