All Scalar API Client responses aren't able to render claiming a missing Content-Type header
martinezdylan opened this issue · 1 comments
martinezdylan commented
Bug description
All of our endpoints are failing to render within the Scalar API Client with it claiming a missing header Content-Type
is missing. We've confirmed the the right headers are found in the response & it works in Postman as well as CURL. See below:
How to reproduce
- Navigate to
https://docs.libum.io/nexum/symxchange/api-reference/persistent/informationservice
- Click "Test it"
- Ping me for an API key & use it as Bearer token
- Click "Send"
Additional context
This was working as recently as July 17th, 2024. I'm not sure what changed but need this fixed ASAP if possible.
martinezdylan commented
adding @nguyendon / @SamyPesse / @addisonschultz for vis