Users
Identify user
Changed onCreate or update a user with the provided identification data. When you identify an existing user, the system merges the properties you specify with what is currently set on the user, updating only the fields included in your requests.
put/v1/users/{user_id}
Request
- Base URL: https://api.knock.app
- URL: https://api.knock.app/v1/users/{user_id}
- Auth: HTTP bearer
Path parameters
user_idstring required
The unique identifier of the user.
Request body
Example request
{
"channel_data": {
"97c5837d-c65c-4d54-aa39-080eeb81c69d": {
"tokens": [
"push_token_123"
]
}
},
"email": "ian.malcolm@chaos.theory",
"name": "Dr. Ian Malcolm",
"preferences": {
"default": {
"channel_types": {
"email": true
},
"workflows": {
"dinosaurs-loose": {
"channel_types": {
"email": true
}
}
}
}
},
"timezone": "America/New_York"
}Response
OK
Example response
{
"__typename": "User",
"created_at": null,
"email": "ian.malcolm@chaos.theory",
"id": "user_id",
"name": "Dr. Ian Malcolm",
"updated_at": "2024-05-22T12:00:00Z"
}Changes
- info
added the new optional request property
/////// - info
added the new optional request property
/////// - info
added the new optional request property
/////// - info
added the new optional request property
/////// - info
added the new optional request property
/////// - info
added the new optional request property
///////
- info
- breaking
the request property
///became not nullable - breaking
the
///request property type changed frombooleanto no type - info
added
subschema #1subschema #3to the///request propertyanyOflist
- breaking