403 Forbidden on proactive messaging push to expired guest session

Getting a 403 Forbidden when trying to push a proactive text message to a guest who closed their web chat session three days ago. We’re using the Node.js platform SDK to hit /api/v2/conversations/messaging/events. The guest ID is still valid in our local store, but the original guestToken expired. Passing the stale token in the Authorization header just returns {“errors”:[“Invalid guest token”]}. Tried swapping to a standard OAuth Bearer token instead. The request goes through, but the platform routes it as an agent-initiated message rather than a system notification.

const payload = {
guestId: “a1b2c3-d4e5-f6g7-h8i9-j0k1l2m3n4o5”,
eventType: “text”,
text: { content: “Your order status has changed.” }
};
await client.conversationsApi.postConversationsMessagingEvents(payload);

Docs mention a proactive push endpoint, but it’s buried under the v1 legacy paths. We’ve got a webhook handler already listening for inbound text events, so the routing side is fine. Just need the push to actually land without forcing a full guest re-auth. Not sure if there’s a specific header flag I’m dropping or if the SDK wrapper is stripping it out. The queue is sitting empty.