# Key improvements for 4.1

**URL:** https://community.xibo.org.uk/t/key-improvements-for-4-1/30483
**Category:** Inside Xibo
**Created:** [November 10, 2023, 3:42pm UTC](https://community.xibo.org.uk/t/key-improvements-for-4-1/30483 "2023-11-10T15:42:08Z")
**Posts on this page:** 1
**Showing post:** 25

<div class="post-metadata">

### Author: ![dan](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/dan/32/9115_2.png) [@dan](https://community.xibo.org.uk/u/dan)
#### Post date: [July 31, 2024, 5:06pm UTC](https://community.xibo.org.uk/t/key-improvements-for-4-1/30483/25 "2024-07-31T17:06:10Z")

</div>

Are you referring to this feature request? This has not made it onto the list yet.

> [@Send dataset post request as JSON](https://community.xibo.org.uk/t/send-dataset-post-request-as-json/30586):
>
> For the original poster (OP) to fill in: Introduction We have APIs that require sending a body formatted as a JSON. Currently the field “Data to add to this request” changes the data to URl encoded characters, causing the request to fail. User Story guardicore, Cisco, and others require a JSON (JWT) formatted body to get a response back. url: https://guardicore\_endpoint/api/v3.0/authenticate body: {"username": "\<username\>", "password": "\<password\>"} URL: https:// api.us.etd.cisco.com/v1/mess…

The complexity here is not so much with the content type of the request, but more that 2 requests are required, and really the first request to get a token should be cached until it expires.

However you could do this already in PHP with a little custom task which makes the requests you need and updates the DataSet’s data.

* * *

As a side note we are working on a better way to collect feature requests and feedback, so that we have a better idea what is commonly requested and/or urgent, which we will feed into our roadmap. More on that soon.

---

_[View the full topic](https://community.xibo.org.uk/t/key-improvements-for-4-1/30483)._
