Validate a signature token and return the associated chat user.
Exchanges a short-lived signed token (HMAC-style proof of chat user identity, payload is the chat user key) for the chat user record it binds to. Anonymous endpoint — the token itself is the credential, so it must be treated as a bearer secret and only delivered to the intended end-user over a confidential channel. Returns 404 if the token signature is invalid, the token is expired, or the bound chat user no longer exists. Typically called by an embedded signature-capture form before `POST`ing the image to the same signature route.
Path Parameters
The tenant identifier
Query Parameters
The signature validation token.
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/chatUsers/signature:validate"{
"identifier": "string",
"provider": "string",
"firstName": "string",
"lastName": "string",
"avatarUrl": "string",
"signatureUrl": "string",
"tenantId": "00000000-0000-0000-0000-000000000000",
"createdAt": 0,
"modifiedAt": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}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.
Lists conversations for a connector.
Returns a paginated list of conversations from an external connector (e.g., Slack channels, Teams chats) that the agent has participated in.