# Foundry API Endpoint To Update User Email **URL:** \ **Category:** Ask the Community\ **Tags:** authentication\ **Created:** [June 13, 2025, 3:50am UTC](https://community.palantir.com/t/foundry-api-endpoint-to-update-user-email/4205 "2025-06-13T03:50:20Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![comad123](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@comad123](https://community.palantir.com/u/comad123)\ **Post date:** [June 13, 2025, 3:50am UTC](https://community.palantir.com/t/foundry-api-endpoint-to-update-user-email/4205/1 "2025-06-13T03:50:20Z")
Is there an endpoint that will allow me to change user details? I see endpoints in the API docs that get user information but nothing that will update user details. I have a webhook that will invoke the “user update” Foundry API endpoint once I find it. Is this possible? Or is there no documentation to update user details because this isn’t possible through the API? ---
**Author:** ![nicornk](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/nicornk/32/192_2.png) [@nicornk](https://community.palantir.com/u/nicornk)\ **Post date:** [June 13, 2025, 4:39am UTC](https://community.palantir.com/t/foundry-api-endpoint-to-update-user-email/4205/2 "2025-06-13T04:39:37Z")
Usually, the email comes in from the IdP through a SAML Mapping. If it’s updated in the IdP Foundry will pick it up automatically. ---
**Author:** ![comad123](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@comad123](https://community.palantir.com/u/comad123)\ **Post date:** [June 13, 2025, 1:49pm UTC](https://community.palantir.com/t/foundry-api-endpoint-to-update-user-email/4205/3 "2025-06-13T13:49:33Z")
Thanks @nicornk . That is our setup, but when our client organization changed their Active directory to send lower-cased email addresses when they used to send them in sentence-case, the users can’t log in (I suspect) because in foundry each user’s email address is sentence-cased. So I wanted to change the case of the email in Foundry to match what is coming in via SAML to test this theory and fix logins. Taking a step back, though. As a secondary question, if the customer org changes the case of the email they send in, would that break authentication? Is Foundry auth case-sensitive? I hoped that whatever came in via IDP would overwrite what is pre-existing in Foundry if there’s a difference, but that might not be the case. Any info is appreciated, thank you! ---
**Author:** ![nicornk](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/nicornk/32/192_2.png) [@nicornk](https://community.palantir.com/u/nicornk)\ **Post date:** [June 13, 2025, 3:31pm UTC](https://community.palantir.com/t/foundry-api-endpoint-to-update-user-email/4205/4 "2025-06-13T15:31:39Z")
It really depends on what was selected as user id in the initial mapping. If the team made the mistake to use the e-mail (which is never a good idea, e.g. people change their name) you are in a bad spot. I have the feeling this is the case for you. Two options: 1. you can use transformation rules on the IdP side to bring back the old user ids 2. you take foundry offline and run a manual migration with some kind of admin account. I have never done this but I am pretty sure it’s possible with Palantir support. ---
**Author:** ![comad123](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@comad123](https://community.palantir.com/u/comad123)\ **Post date:** [June 16, 2025, 7:09am UTC](https://community.palantir.com/t/foundry-api-endpoint-to-update-user-email/4205/5 "2025-06-16T07:09:23Z")
The “offline” option is more feasible although still hard for us to do because of our non-standard install of Foundry…for example emails as user ids. I will look into this approach. Thanks. ---
**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\ **Post date:** [June 11, 2026, 7:10am UTC](https://community.palantir.com/t/foundry-api-endpoint-to-update-user-email/4205/6 "2026-06-11T07:10:04Z")
This topic was automatically closed 360 days after the last reply. New replies are no longer allowed.