# List archived files API does not behave like List meetings API despite same spec

**URL:** <https://devforum.zoom.us/t/list-archived-files-api-does-not-behave-like-list-meetings-api-despite-same-spec/120496>\
**Category:** API and Webhooks\
**Created:** [November 7, 2024, 4:16am UTC](https://devforum.zoom.us/t/list-archived-files-api-does-not-behave-like-list-meetings-api-despite-same-spec/120496 "2024-11-07T04:16:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![administrator2](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@administrator2](https://devforum.zoom.us/u/administrator2)\
**Post date:** [November 7, 2024, 4:16am UTC](https://devforum.zoom.us/t/list-archived-files-api-does-not-behave-like-list-meetings-api-despite-same-spec/120496/1 "2024-11-07T04:16:55Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**  
GET /archive\_files (Meetings \> Archiving docs section)  
GET /users/{userId}/meetings (Meetings \> Meetings docs section)

**Description**  
The two APIs listed should accept pretty much the same headers and query parameters according to the Zoom API docs. But the /archive\_files API complains about bad request, whereas the /meetings API works fine.  
I am accessing these and other Zoom APIs programmatically using C#/.NET 6 (IHttpClientFactory)  
Tried replacing underscore with %5f.

**Error?**  
Bad Request : URL  
—\> System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request)

**How To Reproduce**  
_Steps to reproduce the behavior:_

Method: GET, RequestUri, Version: 1.1, Content: System.Net.Http.StringContent, Headers:  
{  
Authorization: Bearer eyJzdiI6IjAwMDAwMSIsImFsZyI6IkhTNTEyIiwidiI6IjIuMCIsImtpZCI6ImI0ODBkOTkwLWUzZDUtNGNhYy1hNTI1LWM3ZTkxMWRiMmU3MyJ9.eyJ2ZXIiOjEwLCJhdWlkIjoiMWE5YTU4MzQ0ODM3MmM2N2RhYzA0ODU0MDAxZGU5ZWY1NjkxZTYwYjQ5NDYyODlkZTE1OGRjNTkwN2NlYjc4MCIsImNvZGUiOiJIeWJ2UFozMjRtYUlDNkl1MldxU0ZLRTFjaEo2UGRDT0EiLCJpc3MiOiJ6bTpjaWQ6U04zZTVZYVRSV09OQW1kc1hWcnJpQSIsImdubyI6MCwidHlwZSI6MCwidGlkIjowLCJhdWQiOiJodHRwczovL29hdXRoLnpvb20udXMiLCJ1aWQiOiIzN0NsV3p5clNWNkxsNF9GZDBYS2hBIiwibmJmIjoxNzMwOTQ4NTU1LCJleHAiOjE3MzA5NTIxNTUsImlhdCI6MTczMDk0ODU1NSwiYWlkIjoiZUsyak9sWEVSZXFieTBId2ctUDRJdyJ9.swdxyV20jYclJhDkEW7SFgNOuxU2U3BtaIx-1jfXnGh78y0RaRZ6bV\_ghPRtW7a6tU4JlaaRLXK5Kf2nVMTZsQ  
Content-Type: text/plain; charset=utf-8  
}

---

<div class="post-metadata">

**Author:** ![administrator2](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@administrator2](https://devforum.zoom.us/u/administrator2)\
**Post date:** [November 15, 2024, 11:04am UTC](https://devforum.zoom.us/t/list-archived-files-api-does-not-behave-like-list-meetings-api-despite-same-spec/120496/2 "2024-11-15T11:04:39Z")

</div>

Nevermind, I got confused with the error sub-code in the body being 200 for http error code 400. Please disregard this question

HTTP/2 400  
{“code”:200,“message”:"Not available for this account,

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [November 18, 2024, 4:14am UTC](https://devforum.zoom.us/t/list-archived-files-api-does-not-behave-like-list-meetings-api-despite-same-spec/120496/3 "2024-11-18T04:14:07Z")

</div>

Closed on November 18, 2024, 4:14am UTC