# REST APIs Response Header: UTF8 vs UTF-8 vs Blank **URL:** \ **Category:** API and Webhooks\ **Created:** [December 20, 2024, 5:17am UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791 "2024-12-20T05:17:16Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![dalzamendi](https://avatars.discourse-cdn.com/v4/letter/d/aca169/32.png) [@dalzamendi](https://devforum.zoom.us/u/dalzamendi)\ **Post date:** [December 20, 2024, 5:17am UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/1 "2024-12-20T05:17:16Z")
Hi, We have been importing information from many APIs using Azure Data Factory. The charset ‘utf8’ from the response header content-type is not supported because it should be ‘utf-8’ with a hyphen. We discovered this issue while trying to import data from interactions. Would it be possible to fix it/remove it for interactions? /qm/interactions returns: content-type: application/json; charset= **utf8** /contact\_center/engagements returns: content-type: application/json /report/operationlogs returns: content-type: application/json;charset=UTF-8 ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [December 26, 2024, 7:29pm UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/2 "2024-12-26T19:29:42Z")
Hi @dalzamendi Thanks for reaching out to us! Can you confirm that this is only happening with this endpoint: /qm/interactions ? Or do you see this issue in other endpoints too? ---
**Author:** ![dalzamendi](https://avatars.discourse-cdn.com/v4/letter/d/aca169/32.png) [@dalzamendi](https://devforum.zoom.us/u/dalzamendi)\ **Post date:** [January 1, 2025, 9:06pm UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/3 "2025-01-01T21:06:31Z")
We only see that inconsistency it in that endpoint (interactions) for now, we have done work with other endpoints like: agents\_time\_sheets dispositions engagements flows queues queues\_details queues\_metrics users voice\_calls operations and haven’t had any issues. ---
**Author:** ![dalzamendi](https://avatars.discourse-cdn.com/v4/letter/d/aca169/32.png) [@dalzamendi](https://devforum.zoom.us/u/dalzamendi)\ **Post date:** [January 2, 2025, 10:20pm UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/4 "2025-01-02T22:20:12Z")
There seems to be other issues with this endpoint. 1. Max page limit in the documentation is 300. But when executing: {{baseUrl}}/qm/interactions?to=2024-11-31T23:59:59Z&from=2024-11-01T00:00:00Z&page\_size=101 2. There appears to be a cap of 10,000 records. For example, in October, we have significantly more than 10,000 records, but the query: ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [January 3, 2025, 12:41am UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/5 "2025-01-03T00:41:04Z")
Hey @dalzamendi I will send you a DM so you can share more information about this Follow up accordingly please ---
**Author:** ![dalzamendi](https://avatars.discourse-cdn.com/v4/letter/d/aca169/32.png) [@dalzamendi](https://devforum.zoom.us/u/dalzamendi)\ **Post date:** [January 8, 2025, 1:08am UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/6 "2025-01-08T01:08:16Z")
Adding one more inconsistency for this endpoint: It seems that the ‘duration’ column is returning the duration rounded to minutes, rather than in seconds, which is the normal value across other endpoints ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [January 10, 2025, 5:52pm UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/7 "2025-01-10T17:52:18Z")
Hi @dalzamendi I confirmed with our Engineering team that the response header issue is not a bug but a field returned uniformly by the OpenAPI Gateway, so there is no optimization for us to make here. I am still looking into the duration field ---
**Author:** ![dalzamendi](https://avatars.discourse-cdn.com/v4/letter/d/aca169/32.png) [@dalzamendi](https://devforum.zoom.us/u/dalzamendi)\ **Post date:** [January 14, 2025, 6:53am UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/8 "2025-01-14T06:53:45Z")
> [@elisa.zoom](#): > > I confirmed with our Engineering team that the response header issue is not a bug but a field returned uniformly by the OpenAPI Gateway, Hi, Thanks for the feedback. My point is that UTF-8 is the correct encoding name, not UTF8. There are .NET libraries that will not identify UTF8 as a valid encoding name. It just doesn’t make sense, especially when all the other endpoints don’t have this problem. ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [January 16, 2025, 4:09pm UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/9 "2025-01-16T16:09:36Z")
I understand David and I will re share this with our team ---
**Author:** ![Keith2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/keith2/32/69035_2.png) [@Keith2](https://devforum.zoom.us/u/Keith2)\ **Post date:** [May 8, 2025, 1:32am UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/10 "2025-05-08T01:32:08Z")
Hi, I was seeking an update please on the UTF-8 issue, we have implemented a work around, but it is running into other issues failing our loads. We are seeking call this API the same manner as others which work ok, as they are not impacted by this UTF8 / UTF-8 anomaly. Thanks Keith ---
**Author:** ![Keith2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/keith2/32/69035_2.png) [@Keith2](https://devforum.zoom.us/u/Keith2)\ **Post date:** [May 8, 2025, 1:35am UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/11 "2025-05-08T01:35:18Z")
Can we please get an update on this issue. ---
**Author:** ![desautelsj](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/desautelsj/32/23584_2.png) [@desautelsj](https://devforum.zoom.us/u/desautelsj)\ **Post date:** [May 8, 2025, 2:04pm UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/12 "2025-05-08T14:04:38Z")
@dalzamendi I alerted Zoom support of this problem back in December 2016 (yes, you read that right: 8 1/2 years ago!). I had discovered that some of their endpoints returned the misspelled `utf8` charset name instead of the correct spelling which, as you pointed out, is `utf-8`. After some back and forth, the support person who was helping me said that their engineering team declared they were not going to fix the problem because _ **some** _ programing languages are able to overlook this misspelling and automatically fallback to `utf-8`. In their opinion, it didn’t matter that the `HttpClient` class in .NET was rejecting the invalid value and throwing an exception. This is a problem in .NET when you invoke the `ReadAsStringAsync` method of the `HttpClient` class because it tries to automatically determine how the content was encoded and tries to use the appropriate encoding to convert the payload back into a string. This logic breaks when the http response contains an invalid and/or misspelled charset name because the misspelled value does not correspond to any known encoding. In this scenario, Microsoft’s HttpClient throws an exception because it doesn’t know how to handle this unknown charset name. Because Zoom is not likely to ever resolve this problem (someone please correct me if I am assuming incorrectly), you need to look for an alternative and let me suggest two: **Suggestion number 1** : You can use the `ReadAsStreamAsync` method of the `HttpClient` class and try to determine the encoding by yourself in order to convert the content of the stream into a string. You would basically be recreating the logic of Microsoft’s ReadAsStringAsync except you would contend with the aforementioned misspelling and implement a fallback logic when you discover an invalid charset name. **Suggestion number 2** : Instead of trying to resolve the problem yourself, I recommend you use [ZoomNet](https://www.nuget.org/packages/ZoomNet) which is an open source .NET client for the Zoom API (disclaimer: I’m the author). This “misspelled charset name” problem is automatically handled for you in this library using the logic I described in my previous suggestion, so you no longer have to worry about this specific problem. There are many other benefits to using this library but I am only highlighting this one because it is specifically relevant to the problem you are facing. Let me know if any of this is useful to you ---
**Author:** ![desautelsj](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/desautelsj/32/23584_2.png) [@desautelsj](https://devforum.zoom.us/u/desautelsj)\ **Post date:** [May 8, 2025, 8:13pm UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/13 "2025-05-08T20:13:56Z")
@Keith2 I meant to tag you as well in my answer above. Sorry about that. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\ **Post date:** [May 12, 2026, 11:50am UTC](https://devforum.zoom.us/t/rest-apis-response-header-utf8-vs-utf-8-vs-blank/122791/14 "2026-05-12T11:50:23Z")
Closed on May 12, 2026, 11:50am UTC This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.