Skip to main content
Solved

How to get Conversations API access enabled (send + read WhatsApp conversation messages)?

  • July 9, 2026
  • 2 replies
  • 67 views

Hi all,

  We're an ecommerce brand (Shopify + Klaviyo) using Klaviyo WhatsApp as our
  customer support channel, and we're building an internal dashboard that
  unifies email + WhatsApp conversations in one place.

  The docs for `POST /api/conversation-messages` (Create Conversation Message)
  say: "Requires account-level enablement. To request access, reach out in the
  developer community." — so here I am 🙂

  Two questions:

  1. Could someone from Klaviyo enable the Conversations API
     (`conversations:read` / `conversations:write` scopes) for our account?
     Happy to share our account ID privately.

  2. Is there any way to READ the messages a customer sends us on WhatsApp via
     the API? Outbound messages show up nicely in the Events API with full
     message body (Sent/Relayed/Received WhatsApp metrics), but I can't find
     any endpoint or metric that exposes inbound customer messages.
     `GET /api/profiles/{id}/conversation` only returns the conversation ID and
     channel. Is inbound message history on the roadmap, or already possible
     with the enablement?

  Our use case: read-only sync of conversations into our own dashboard, plus
  replying to open conversations from it (respecting the 24h customer service
  window).

Best answer by Temi O.

Hi ​@nstassart , 

 

Thank you for reaching out! To request access, you will need to submit the form here: https://docs.google.com/forms/d/e/1FAIpQLSfERSXubqcQOjYVMpEH-D-U8y23Pl-KpHp4WDjG1w3LRc8faA/viewform

Regarding ability to read WhatsApp messages: from what I’ve found, Klaviyo appears to support inbound WhatsApp processing internally and in Helpdesk/integrations, but we don’t have evidence of a public API endpoint that exposes inbound WhatsApp message history/body. GET /api/profiles/{id}/conversation returning only conversation metadata or null for WhatsApp appears consistent with current limitations or account-level enablement gaps.

I know there is an active internal escalation pattern around WhatsApp conversation retrieval, but no confirmed public roadmap commitment for inbound history exposure.

I’d be very curious if anyone here has this working already and can confirm whether inbound WhatsApp history is available in any way today with the current enablement! 

 


Temi@Klaviyo

2 replies

whereisjad
Expert Problem Solver IV
Forum|alt.badge.img+20
  • Expert Problem Solver IV
  • July 9, 2026

@nstassart I believe this is something you have to direct to Customer Support via here https://help.klaviyo.com/hc/en-us/articles/115001002272

 


Temi O.
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • Answer
  • July 13, 2026

Hi ​@nstassart , 

 

Thank you for reaching out! To request access, you will need to submit the form here: https://docs.google.com/forms/d/e/1FAIpQLSfERSXubqcQOjYVMpEH-D-U8y23Pl-KpHp4WDjG1w3LRc8faA/viewform

Regarding ability to read WhatsApp messages: from what I’ve found, Klaviyo appears to support inbound WhatsApp processing internally and in Helpdesk/integrations, but we don’t have evidence of a public API endpoint that exposes inbound WhatsApp message history/body. GET /api/profiles/{id}/conversation returning only conversation metadata or null for WhatsApp appears consistent with current limitations or account-level enablement gaps.

I know there is an active internal escalation pattern around WhatsApp conversation retrieval, but no confirmed public roadmap commitment for inbound history exposure.

I’d be very curious if anyone here has this working already and can confirm whether inbound WhatsApp history is available in any way today with the current enablement! 

 


Temi@Klaviyo