Skip to content
V2 (Legacy) API ReferenceGet started
Messaging

Voice Memos

Send audio as an iMessage voice memo with native inline playback.

Voice memos are sent through a dedicated endpoint. On iMessage, they render with the native inline audio player — the voice-memo bubble you get when recording in the Messages app. On RCS and SMS, this endpoint falls back to a regular audio attachment, which is the same result you’d get from sending the audio as a media part via the standard send-message flow. In practice the endpoint is useful when you specifically want the iMessage voice-memo affordance for iMessage-capable recipients; for RCS/SMS delivery you can use either path (see Protocol Selection).

The request body takes a single field, voice_memo_url, which must be a publicly accessible HTTPS URL. There is no attachment_id alternative — voice memos are always URL-sourced. See the Send Voice Memo API reference for the full endpoint specification.

Terminal window
curl -X POST https://api.linqapp.com/api/partner/v3/chats/{chat_id}/voicememo \
-H "Authorization: Bearer $LINQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"voice_memo_url": "https://example.com/voice-memo.m4a"
}'
await client.chats.sendVoicememo(chatId, {
voice_memo_url: 'https://example.com/voice-memo.m4a',
});
client.chats.send_voicememo(
chat_id,
voice_memo_url="https://example.com/voice-memo.m4a",
)
FormatMIME type
MP3audio/mpeg
M4Aaudio/x-m4a, audio/mp4
AACaudio/aac
CAFaudio/x-caf
WAVaudio/wav
AIFFaudio/aiff, audio/x-aiff
AMRaudio/amr
  • iMessage-specific affordance — The inline voice-memo bubble is iMessage-only. On RCS and SMS this endpoint delivers the audio as a regular attachment, equivalent to sending a media part via the standard send-message flow — use whichever path is more convenient for those recipients.
  • HTTPS required — The source URL must be publicly reachable with a valid TLS certificate. The API downloads the file before sending.
  • File size — The 10 MB direct-URL limit applies. Larger files should be hosted on a CDN you control.
  • Webhooks — Voice memo delivery is confirmed via the standard message.sent / message.delivered / message.failed events. See Webhooks.