# Important Notice: Enforcing API parameter restrictions

**URL:** <https://community.holistics.io/t/important-notice-enforcing-api-parameter-restrictions/2120>\
**Category:** News from Holistics\
**Created:** [October 1, 2024, 11:25am UTC](https://community.holistics.io/t/important-notice-enforcing-api-parameter-restrictions/2120 "2024-10-01T11:25:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tien\_Truong\_Tran](https://community.holistics.io/user_avatar/community.holistics.io/tien_truong_tran/32/1352_2.png) [@Tien\_Truong\_Tran](https://community.holistics.io/u/Tien_Truong_Tran)\
**Post date:** [October 1, 2024, 11:25am UTC](https://community.holistics.io/t/important-notice-enforcing-api-parameter-restrictions/2120/1 "2024-10-01T11:25:22Z")

</div>

Hi everyone 🙋‍♂️,

This is Tien from the Holistics Engineering team.

As part of our ongoing efforts to enhance the reliability and security of Holistics services, we will be enforcing public API parameter restrictions.

🗓 This change will take effect starting from **December 2024**.

## **What’s changing?** 🚀

### Before

- API clients could send [**Query**](https://en.wikipedia.org/wiki/Query_string) Parameters when the API specification requires [**Body**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Messages#body) Parameters, and vice versa.

### After

- API clients will have to send parameters correctly in **Query** or **Body**  **as specified in our API specification.** Otherwise, the API requests would be rejected.

## **What you need to do** 💡

* * *

💡 If you are already using Holistics API as specified on [Holistics API | Holistics Docs (4.0)](https://docs.holistics.io/api), you don’t need to change anything.

* * *

Please double-check your API client and make sure to pass the parameters correctly as outlined in our [Public API specification](https://docs.holistics.io/api).

- [Example](https://docs.holistics.io/api#tag/Users/operation/Users_CheckHolisticsUser) of an API that requires Query parameter:  

- [Example](https://docs.holistics.io/api#tag/Users/operation/Users_Invite) of an API that requires Body parameter:  

Here are some incorrect versus correct ways to pass parameters (`emails` and `role`) when using the API [Invite Users](https://docs.holistics.io/api/#tag/Users/operation/Users_Invite).

- Using `curl`

- Using `JS fetch`

## **What will happen starting from December 2024?** 🗓

Starting from December 2024, any API calls with incorrectly formatted parameters will receive a `400 Bad Request` error.

## **Feedback** 📝

If you have any further concerns, please comment below or contact us at [support@holistics.io](mailto:support@holistics.io).

Cheers & all the best! 🍻

---

<div class="post-metadata">

**Author:** ![Tien\_Truong\_Tran](https://community.holistics.io/user_avatar/community.holistics.io/tien_truong_tran/32/1352_2.png) [@Tien\_Truong\_Tran](https://community.holistics.io/u/Tien_Truong_Tran)\
**Post date:** [December 13, 2024, 2:59am UTC](https://community.holistics.io/t/important-notice-enforcing-api-parameter-restrictions/2120/2 "2024-12-13T02:59:32Z")

</div>

Hi everyone 🙋‍♂️,

The restriction policy has been in effect since yesterday, **December 12th**.

If you are getting errors with status 400 when requesting our public API, please double-check your API client and make sure to pass the parameters correctly as outlined in our [Public API specification](https://docs.holistics.io/api).

If you have any further concerns, please comment below or contact us at [support@holistics.io](mailto:support@holistics.io).

Thank you