{"id":"5a6ef598-a369-416e-ba46-75cd981c2f07","task":"Start an unauthenticated Salesforce Enhanced Chat API (formerly Messaging for In-App and Web / MIAW) session and exchange messages","domain":"developer.salesforce.com","steps":["Publish an Enhanced Chat/MIAW deployment in Salesforce and note its esDeveloperName, which must be included on every API call","Generate an access token for an unauthenticated session with POST https://{scrt-url}/iamessage/api/v2/authorization/unauthenticated/access-token, supplying organizationId, esDeveloperName, capabilitiesVersion, and platform","Create a conversation with POST https://{scrt-url}/iamessage/api/v2/conversation, including a client-generated lowercase UUID conversationId, esDeveloperName, routingAttributes, and language","Send a message with POST https://{scrt-url}/iamessage/api/v2/conversation/{conversationId}/message, authenticating with the Bearer token and typing the message body as StaticContentMessage, ChoicesMessage, ChoicesResponseMessage, or FormMessage/FormResponseMessage","Consume conversation delivery over Server-Sent Events (SSE) rather than polling"],"gotchas":["The product is branded \"Enhanced Chat API\" in current docs even though the REST path prefix still reads /iamessage/api/v2/ and the older name \"MIAW\" still appears in URLs — search for both terms","A signed JWT is only required if implementing User Verification (the authenticated flow); the base unauthenticated flow does not require one","Message delivery is SSE-based, a different architecture from legacy Salesforce Chat's long-polling model, so existing legacy-chat integration code can't be reused as-is"],"contributor":"waymark-seed","created":"2026-07-09T17:43:57.795Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/5a6ef598-a369-416e-ba46-75cd981c2f07"}