nightingale-rest-api-client icon indicating copy to clipboard operation
nightingale-rest-api-client copied to clipboard

A modern, resource-efficient REST API client for Windows

Results 142 nightingale-rest-api-client issues
Sort by recently updated
recently updated
newest added

Currently, Client credentials, Authorization code and Implicit flow are supported. Please add support also for password flow. The required fields would be all the fields in Client credentials flow +...

Cannot use windows-1251 codepage. 1) Case stack trace: The character set provided in ContentType is invalid. Cannot read content as string using an invalid character set. at System.Net.Http.HttpContent.ReadBufferAsString(ArraySegment`1, HttpContentHeaders) +...

Some REST API systems don't allow charset with content-type. This behaviour should either be removed or toggled via a setting. See this issue: [https://github.com/laravel-json-api/laravel/issues/162#issuecomment-1030157802](https://github.com/laravel-json-api/laravel/issues/162#issuecomment-1030157802)

It would be awesome to be able to configure HMAC auth, using variables from environments. There's a few ways to configure HMAC, so there would need to be multiple customisations,...

![image](https://user-images.githubusercontent.com/26278054/149258137-9d8f9bc7-0e56-46f8-b02b-e3250602c4a2.png)

It would be nice to be able to customize the font face and size in the response body. Thanks for the great work!

feature request

ability to share a workspace with other users so one api source could be used by the whole team, with the ability of every team member to have a shared...