# SSO en gefilterde IP's

**URL:** https://meta.discourse.org/t/sso-and-screened-ips/172638
**Category:** SSO
**Tags:** rest-api
**Created:** [8 december 2020 om 14:44 UTC](https://meta.discourse.org/t/sso-and-screened-ips/172638 "2020-12-08T14:44:19Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![mentalstring](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mentalstring/32/168934_2.png) [@mentalstring](https://meta.discourse.org/u/mentalstring)
#### Post date: [8 juni 2021 om 10:53 UTC](https://meta.discourse.org/t/sso-and-screened-ips/172638/6 "2021-06-08T10:53:50Z")

</div>

I had already done that and the deleting API endpoint is the one I have been using, which the same one for both actions (delete only and delete&block) — the only difference is on the parameters that are used with it (`block_ip`, `block_email`, …) that I mentioned aboved.

> [@mentalstring](#):
>
> However, we are issuing the DELETE request using `block_ip=false` . This is from rails logs:
> 
> ```plaintext
> Parameters: {"delete_posts"=>"1", "block_email"=>"0", "blocked_urls"=>"0", "block_ip"=>"0", "id"=>"123"}
> 
> ```

I think I finally got around what was the issue with my requests: Discourse’s API wants the strings ‘true’ and ‘false’ instead truthy/falsy values. My bad for not spotting the notice about that on the [docs](https://docs.discourse.org/).

That was probably what has been causing all [this mess](https://meta.discourse.org/t/sso-and-blocked-ip-addresses/192588/6).

---

_[View the full topic](https://meta.discourse.org/t/sso-and-screened-ips/172638)._