Use case
Retrieve call recording access and associated SMS replies for post-call customer experiences.Public recording flow
- Customer accesses short-code route (for example public recording page).
- Platform resolves short code to recording context.
- Playback is available only when source URL is valid/accessible.
SMS replies flow
- Query SMS replies associated with the recording short code via API route.
- Use replies to display post-call conversation context in your app/support flows.
URL validity assumptions
- Recording source URLs can expire or become unavailable over time.
- A valid short code does not guarantee active recording URL forever.
- Clients should handle unavailable/expired recording states gracefully.
Expected user-visible outcomes
- Valid short code + valid source URL: recording playable, replies visible if present.
- Valid short code + invalid/expired URL: recording unavailable message; replies may still be visible.
- Invalid short code: not found/unavailable state.
Integration guidance
- Cache minimal metadata only; do not assume perpetual URL validity.
- Handle empty reply sets as a normal state.
- Log short code + timestamp for support diagnostics.
Troubleshooting
Recording unavailable for known short code
- Confirm source URL validity and expiry policy in your environment.
- Retry later if source availability is transient.
No SMS replies returned
- Confirm replies exist for that conversation.
- Validate short code mapping to the intended call.