# Exist The Conversation Exist URL endpoint can be used to check if a conversation exists based on unique id, user id or user phone number. ### Request The following request will generate a new Share URL: ```bash curl --location --request GET 'https://.xenioo.com/conversation/exists/' \ --header 'Authorization: Bearer ' \ ``` The mode parameter can have the following values | Value | Description | | ----- | ---------------------------------------------------------------------------------------- | | query | It can be either the unique id of the conversation, the user id or the user phone number | ### Response The call doesn't return anything but the relevant response code. ### Response Codes This endpoint will reply with the following standard HTTP codes. | Code | Meaning | | ---- | ------------------------------------------------------------------- | | 200 | Success. The conversation exist. | | 400 | Bad Request. The supplied token is not authorized to this request. | | 401 | Unauthorized. The account associated to the token is not authorized | | 404 | Not Found. The specified conversation has not been found | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs10.xenioo.com/xenioo-api/globa-platform-api/conversations/exist.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.