Retrieves a specific chat user.
Looks up an end-user (someone who talks to agents via a connector like Slack/Discord/web chat) by their composite `provider:identifier` key. Distinct from tenant `Users` — chat users are external identities scoped to the connector that produced them, not workspace members. Returns 404 if no chat user with that key has been seen in this workspace. Use `GET /chatUsers` to discover keys.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The chat user key in format provider:identifier (e.g., telegram:123456).
The tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/chatUsers/string"{
"key": {
"identifier": "string",
"provider": "string"
},
"firstName": "string",
"lastName": "string",
"avatarUrl": "string",
"signatureUrl": "string"
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Lists all chat users.
Returns all users who have interacted with agents via chat interfaces or external connectors.
Update a chat user's signature image.
Stores a captured signature image against the chat user identified by `token`. If the user already had a signature on file, the previous image is deleted from storage after the new one is uploaded. Multipart upload; the `signature` part's content type is preserved and used when the image is served back. Anonymous, but the signed token gates access — callers must obtain it via `GET ...:validate` first. The token is a self-signed bearer credential and remains usable until expiry, so repeated calls with the same token will overwrite the signature.