# Deleting object by API is deleting from one end point / satellite not from the other

**URL:** <https://community.icinga.com/t/deleting-object-by-api-is-deleting-from-one-end-point-satellite-not-from-the-other/10023>\
**Category:** Icinga 2\
**Tags:** api\
**Created:** [June 22, 2022, 9:25am UTC](https://community.icinga.com/t/deleting-object-by-api-is-deleting-from-one-end-point-satellite-not-from-the-other/10023 "2022-06-22T09:25:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shams](https://community.icinga.com/letter_avatar_proxy/v4/letter/s/e99b99/32.png) [@Shams](https://community.icinga.com/u/Shams)\
**Post date:** [June 22, 2022, 9:25am UTC](https://community.icinga.com/t/deleting-object-by-api-is-deleting-from-one-end-point-satellite-not-from-the-other/10023/1 "2022-06-22T09:25:52Z")

</div>

Hi, at our setup we got 1 master and 2 satellites / end points. When we are pushing host config and service config by api those are going at the master and the 2 satellites / end points. However, when we are deleting by api the config files are getting deleted from the master and 1 satellite / end point. However, it is not showing at Icinga2 web also after deleting. But at other satellite / end point the config files are still there.

We need to keep same host config files and service config files at both the satellites / end points so that if one is failed, the other can work.