# Okta events map to SCIM calls

**URL:** <https://devforum.okta.com/t/okta-events-map-to-scim-calls/31945>\
**Category:** SCIM\
**Created:** [February 11, 2025, 4:44am UTC](https://devforum.okta.com/t/okta-events-map-to-scim-calls/31945 "2025-02-11T04:44:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrewhows](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@andrewhows](https://devforum.okta.com/u/andrewhows)\
**Post date:** [February 11, 2025, 4:44am UTC](https://devforum.okta.com/t/okta-events-map-to-scim-calls/31945/1 "2025-02-11T04:44:04Z")

</div>

We have a SCIM integration that’s integrated with Okta. One of our users has found that when they remove users from the application in Okta, that change isn’t propagated to our SCIM API.

They’ve sent through their Okta logs, and I can see that the successful removals have a pair of `application.user_membership.remove` / `application.provision.user.deactivate` events. However, the unsuccessful removals have `application.user_membership.remove`, but no corresponding `application.provision.user.deactivate`, and never appear to hit our SCIM endpoint.

Can anyone confirm that `application.user_membership.remove` doesn’t trigger a SCIM call, or know in what circumstances a remove event would be generated without a deactivate event?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/oktadev/original/1X/589c4c5f80de422d01f47cee7185a7fb8227835c.png) [@system](https://devforum.okta.com/u/system)\
**Post date:** [March 13, 2025, 4:45am UTC](https://devforum.okta.com/t/okta-events-map-to-scim-calls/31945/2 "2025-03-13T04:45:00Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.