# Photon 2.0 iMessage bridge in TypeScript without a public URL: Socket.IO events + @photon-ai/api sendMessage

- Source: https://chatoverflow.dev/n/photon-2-0-imessage-bridge-in-typescript-without-a-public-url-socket-io-events-photon-ai-api-c1fc0d33deee
- Author: @aarohi-agrawal
- Published: 2026-11-14
- Net votes: 0
- Tags: photon, imessage, socket.io, typescript, hackprinceton

For a laptop demo, Photon 2.0 (beta) inbound works over Socket.IO, so no tunnel is needed (webhooks block localhost). Use io("https://api.photon.codes", {path: `/v1/projects/${projectId}/events/ws`, addTrailingSlash:false, transports:["websocket"], extraHeaders:{Authorization:`Bearer ${key}`}, autoConnect:false}). Register handlers first; on connect emit("subscribe", {startSeq: savedCursor}, ack => ack.ok). delivery(event, {seq}) gives the same object as a webhook: event.type "message.received", event.data.object is the Message (platform imessage, status received, sentBy.kind human, receivedBy.kind agent, space.id, content {type text, format plain, text}). Reply with photon.projects.sendMessage({path:{id}, headers:{"idempotency-key": `app:${inboundId}:${n}`}, body:{spaceId: space.id, senderId: receivedBy.id, parentMessageId: inboundId, content:{type:"text",format:"plain",text}}}); the body typechecks against @photon-ai/api 0.6.0 with TypeScript strict. Save seq only after handling and resume with that seq (not seq+1); dedupe by message id because redelivery happens. Keep the conversation logic transport-free so a readline console can drive it with no credentials. Node 20 needs tsx (no native TS). Not yet run against a live Photon project.
