# Unable to access AI companion transcripts from API using /meetings/{encoded-UUID}/transcript

**URL:** <https://devforum.zoom.us/t/unable-to-access-ai-companion-transcripts-from-api-using-meetings-encoded-uuid-transcript/136510>\
**Category:** API and Webhooks\
**Created:** [August 14, 2025, 5:10pm UTC](https://devforum.zoom.us/t/unable-to-access-ai-companion-transcripts-from-api-using-meetings-encoded-uuid-transcript/136510 "2025-08-14T17:10:06Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![CRDR](https://avatars.discourse-cdn.com/v4/letter/c/bb73d2/32.png) [@CRDR](https://devforum.zoom.us/u/CRDR)\
**Post date:** [August 20, 2025, 7:38pm UTC](https://devforum.zoom.us/t/unable-to-access-ai-companion-transcripts-from-api-using-meetings-encoded-uuid-transcript/136510/5 "2025-08-20T19:38:13Z")

</div>

Thanks @elisa.zoom you gave us the clue needed to solve the issue.

We had already been testing with the _scheduled_ UUID but that was not working as mentioned.

After some testing though, we’ve confirmed that the issue stems from Zoom returning two different UUIDs for scheduled and past meetings:

1. **Scheduled meeting UUID**

2. **Instance (past meeting) UUID**

Conclusions:

- `/transcripts` requires the **instance UUID** , not the scheduled UUID.

- Passing the scheduled UUID will return an error even though a transcript exists.

- Instance UUIDs can be obtained via `GET /past_meetings/{meetingId}/instances` or webhooks like `meeting.ended`.

- If the UUID contains `/` or starts with `/`, it must be **double URL-encoded**.

So, we can now retrieve the AI companion transcripts using the past-meeting instance UUID. Hopefully this is helpful to others as well!

---

_[View the full topic](https://devforum.zoom.us/t/unable-to-access-ai-companion-transcripts-from-api-using-meetings-encoded-uuid-transcript/136510)._
