import requests
url = "https://app.langwatch.ai/api/scim/v2/Users/{id}"
payload = {
"schemas": ["<string>"],
"Operations": [
{
"path": "<string>",
"value": "<unknown>"
}
]
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/scim+json"
}
response = requests.patch(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'PATCH',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/scim+json'},
body: JSON.stringify({schemas: ['<string>'], Operations: [{path: '<string>', value: '<unknown>'}]})
};
fetch('https://app.langwatch.ai/api/scim/v2/Users/{id}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request PATCH \
--url https://app.langwatch.ai/api/scim/v2/Users/{id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/scim+json' \
--data '
{
"schemas": [
"<string>"
],
"Operations": [
{
"path": "<string>",
"value": "<unknown>"
}
]
}
'{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User"
],
"id": "<string>",
"userName": "<string>",
"name": {
"givenName": "<string>",
"familyName": "<string>"
},
"emails": [
{
"primary": true,
"value": "<string>",
"type": "<string>"
}
],
"active": true,
"meta": {
"resourceType": "User",
"created": "<string>",
"lastModified": "<string>"
},
"externalId": "<string>"
}{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:Error"
],
"status": "<string>",
"detail": "<string>",
"scimType": "<string>"
}{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:Error"
],
"status": "<string>",
"detail": "<string>",
"scimType": "<string>"
}{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:Error"
],
"status": "<string>",
"detail": "<string>",
"scimType": "<string>"
}{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:Error"
],
"status": "<string>",
"detail": "<string>",
"scimType": "<string>"
}Update a provisioned user
Applies RFC 7644 section 3.5.2 patch operations. What is implemented: replace of active (deactivating or reactivating the account), of userName, and of name.givenName / name.familyName, written either as an operation path or as keys inside a value object; and add, replace or remove of the enterprise costCenter, which reassigns the member’s department. replace, add and remove are the only operation names understood, read without regard to case, so the capitalized Replace that Entra ID writes is accepted; any other name, or a missing or non-string one, is rejected with a 400. An understood operation aimed at anything not listed above is accepted and changes nothing.
import requests
url = "https://app.langwatch.ai/api/scim/v2/Users/{id}"
payload = {
"schemas": ["<string>"],
"Operations": [
{
"path": "<string>",
"value": "<unknown>"
}
]
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/scim+json"
}
response = requests.patch(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'PATCH',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/scim+json'},
body: JSON.stringify({schemas: ['<string>'], Operations: [{path: '<string>', value: '<unknown>'}]})
};
fetch('https://app.langwatch.ai/api/scim/v2/Users/{id}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request PATCH \
--url https://app.langwatch.ai/api/scim/v2/Users/{id} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/scim+json' \
--data '
{
"schemas": [
"<string>"
],
"Operations": [
{
"path": "<string>",
"value": "<unknown>"
}
]
}
'{
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User"
],
"id": "<string>",
"userName": "<string>",
"name": {
"givenName": "<string>",
"familyName": "<string>"
},
"emails": [
{
"primary": true,
"value": "<string>",
"type": "<string>"
}
],
"active": true,
"meta": {
"resourceType": "User",
"created": "<string>",
"lastModified": "<string>"
},
"externalId": "<string>"
}{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:Error"
],
"status": "<string>",
"detail": "<string>",
"scimType": "<string>"
}{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:Error"
],
"status": "<string>",
"detail": "<string>",
"scimType": "<string>"
}{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:Error"
],
"status": "<string>",
"detail": "<string>",
"scimType": "<string>"
}{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:Error"
],
"status": "<string>",
"detail": "<string>",
"scimType": "<string>"
}Authorizations
SCIM token for one organization's directory connection, created with POST /api/scim-tokens or in Settings > SCIM. It authenticates provisioning calls only, and stops working if the organization's Enterprise plan lapses.
Path Parameters
1Response
The updated user.
Was this page helpful?