{"info":{"_postman_id":"1e1f34ea-7d2a-4024-b43a-b37cefdc8e14","name":"SEEYOU API REFERENCE","description":"

Overview

This API reference documentation provides a comprehensive overview of the RESTful, streaming, and real-time interfaces available for interacting with the SEEYOU platform. These APIs enable developers to integrate SEEYOU advanced language processing capabilities into their applications, services, or workflows using standardized communication protocols.

Authentication & Security

All access to SEEYOU APIs requires valid authentication credentials, typically in the form of an API key. Requests must be made over HTTPS to ensure data integrity and confidentiality.

Remember that your API key is a secret! Do not share it with others or expose it in any client-side code (browsers, apps).

Rate Limiting & Usage Quotas

To ensure fair usage and system stability, API calls are subject to rate limits based on account type and plan. Developers can monitor usage metrics through the SEEYOU dashboard and adjust quotas accordingly. Exceeding allocated limits will result in 429 Too Many Requests responses, prompting clients to implement exponential backoff strategies or request quota increases.

Error Handling & Retries

The SEEYOU API employs standard HTTP status codes to indicate success or failure of requests. Errors are categorized as either client errors (4xx) or server errors (5xx), with detailed error messages returned in the JSON body. Clients should implement robust retry logic with jittered backoff when encountering transient failures.

Backward Compatibility Policy

At SEEYOU, we are committed to ensuring long-term stability and reliability for developers integrating our platform. To achieve this, we strive to avoid breaking changes in existing interfaces across major API versions whenever feasible.

This policy applies to the following core components of the SEEYOU ecosystem:

REST API (currently at v1)

Backwards-Compatible Changes

The following types of changes are considered non-breaking and will not require updates to your integration:

Adding new endpoints to the REST API
\n
Introducing optional parameters to existing API methods
\n
Appending new fields to JSON response bodies or event payloads
\n
Reordering properties within JSON objects (as JSON does not enforce field order)
\n
Modifying format or length of opaque identifiers (e.g., UUIDs, resource IDs)
\n
Introducing new event types in streaming or Real-Time API interfaces
\n

API Versioning Strategy

Currently, we implement versioning only at the major API level , which is embedded in the URL path using the v1 identifier (e.g., /api/v1/chat/completion). This ensures that once you integrate with a given version, the contract remains stable throughout its lifecycle.

Minor improvements and non-breaking enhancements are introduced within the same major version, allowing developers to benefit from performance gains, accuracy improvements, and feature additions without requiring immediate code changes.

\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"26951742","collectionId":"1e1f34ea-7d2a-4024-b43a-b37cefdc8e14","publishedId":"2sB2qahgAb","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"e05d19"},"publishDate":"2025-05-30T08:23:13.000Z"},"item":[{"name":"Chat","item":[{"name":"Tones","id":"b6c7dab5-0a66-45f1-b262-510cacfafba4","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Authorization","value":"Bearer SEEYOU_API_KEY"},{"key":"Content-Type","value":"application/json"}],"url":"https://api.seeyou.eu/api/v1/chat/tones","description":"

Chat Tones

The Chat Tones API returns a list of all available tones that can be used to adjust the tone and length of responses. Each tone in the list helps customize how the model replies—whether it should sound short, long or any other. This allows users to fine-tune the style and depth of the answers based on their preferences or use case.

Request Format

Authentication Header

Authorization: Bearer SEEYOU_API_KEY\nContent-Type: application/json\n\n

Body Parameters (None)

\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"SEEYOU_API_KEY"}]},"isInherited":true,"source":{"_postman_id":"1e1f34ea-7d2a-4024-b43a-b37cefdc8e14","id":"1e1f34ea-7d2a-4024-b43a-b37cefdc8e14","name":"SEEYOU API REFERENCE","type":"collection"}},"urlObject":{"protocol":"https","path":["api","v1","chat","tones"],"host":["api","seeyou","eu"],"query":[],"variable":[]}},"response":[{"id":"af004fec-0943-4f95-a556-0d59b3e9d947","name":"Success","originalRequest":{"method":"GET","header":[{"key":"Content-Type","value":"application/json","type":"text"}],"url":"https://api.seeyou.eu/api/v1/chat/tones"},"code":200,"_postman_previewlanguage":"Text","header":[],"cookie":[],"responseTime":null,"body":"[\n {\n \"id\": 1,\n \"tone\": \"Long Professional\",\n \"description\": \"Long Professional\",\n \"prompt\": \"Tone Instructions:\\n\\n**longer-professional:**\\n- **Tone:** longer-professional.\\n- **Response Dialect:** European English with a down-to-earth tone of response.\\n- **Answer Length:** Even for simple queries, always provide a response with a minimum of 2700-3000 characters (excluding spaces). Ensure detailed elaboration, examples, and analysis.\\n- **Emojis:** None.\\n- **Answer Style:** Avoid all embellishments. Use a straightforward European tone. Ensure clarity, professionalism, and a neutral approach.\\n\\n### Format Instructions:\\n1. Always use Markdown # for the main heading.\\n2. Include a summary paragraph (without labeling it as 'summary').\\n3. Use Markdown ## for subheadings to structure the content logically.\\n4. Each subheading should have detailed paragraphs (500–800 characters each).\\n5. Use bullet points to highlight key information.\\n6. End with 'Source Links' using Markdown ## if valid sources are available.\\n7. Always follow the above format except for translation or grammar improvement queries.\\n8. For queries related to seeyouGPT and its founder, responses must exceed 2700 characters with well-structured headings and subheadings.\"\n },\n {\n \"id\": 2,\n \"tone\": \"Short Professional\",\n \"description\": \"Short Professional\",\n \"prompt\": \"Tone Instructions:\\n\\n**short-professional:**\\n- **Tone:** short-professional.\\n- **Response Dialect:** European English with a down-to-earth tone.\\n- **Answer Length:** 1620–1800 characters (excluding spaces). Be concise and focus on key points.\\n- **Emojis:** None.\\n- **Answer Style:** Avoid embellishments. Use a straightforward European tone. Maintain clarity and professionalism.\\n\\n### Format Instructions:\\n1. Use Markdown # for the main heading.\\n2. Include a summary paragraph (do not label it).\\n3. Use Markdown ## for subheadings with concise paragraphs (100–150 characters each).\\n4. Use bullet points where needed.\\n5. Add 'Source Links' in Markdown ## format if sources are available.\\n6. Follow the above format except for translation/improvement queries.\"\n },\n {\n \"id\": 3,\n \"tone\": \"Short, No Subheadings\",\n \"description\": \"Short, No Subheadings\",\n \"prompt\": \"Tone Instructions:\\n\\n**Short, No Subheadings:**\\n- **Tone:** Short, No Subheadings.\\n- **Response Dialect:** European English with a down-to-earth tone.\\n- **Answer Length:** 1350–1500 characters (excluding spaces).\\n- **Emojis:** None.\\n- **Answer Style:** No embellishments. Use a clear and professional tone.\\n\\n### Format Instructions:\\n1. Provide content in a single structured format without headings or subheadings.\\n2. Use bullet points only if needed.\\n3. Add 'Source Links' in Markdown ## format if valid sources are available.\"\n },\n {\n \"id\": 4,\n \"tone\": \"Short w. Emojis\",\n \"description\": \"Short w. Emojis\",\n \"prompt\": \"Tone Instructions:\\n\\n**Short with emojis:**\\n- **Tone:** Short w. Emojis.\\n- **Response Dialect:** European English with a down-to-earth tone.\\n- **Answer Length:** 1350–1500 characters (excluding spaces).\\n- **Emojis:** Always include 3 emojis.\\n- **Answer Style:** No embellishments. Use a clear and professional tone.\\n\\n### Format Instructions:\\n1. Always include 3 emojis.\\n2. Provide content in a unified format without headings or subheadings.\\n3. Add valid 'Source Links' at the end (not in bullet points). Skip if not available.\"\n }\n]"}],"_postman_id":"b6c7dab5-0a66-45f1-b262-510cacfafba4"},{"name":"Models","id":"00bd5ae9-2158-46d0-baa2-0eecd98d23a1","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Authorization","value":"Bearer SEEYOU_API_KEY"},{"key":"Content-Type","value":"application/json"}],"url":"https://api.seeyou.eu/api/v1/chat/models","description":"

Chat Models

This endpoint handles a GET request for Models operation in the SEEYOU API.

Ensure a valid Authorization bearer token is included in the header.
Refer to the API documentation for full details on request and response structure.

Chat Completion

The Chat Completion API endpoint generates a conversational response using SEEYOU’s large language model (LLM), based on a sequence of input messages. It supports both stateless interactions and context-aware threaded conversations via an optional thread_id.

Request Format

Authentication Header

Authorization: Bearer SEEYOU_API_KEY\nContent-Type: application/json\n\n

Body Parameters

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Type	Description
`thread_id`	string (optional)	Unique identifier for maintaining conversation context across multiple requests. Omit to initiate a new, stateless interaction.
`messages`	array (required)	Ordered list of message objects representing the conversation history. Each object must contain `role` and `content`.
`messages.role`	string	Role of the message sender. Valid values: `system`, `user`, or `assistant`.
`messages.content`	string	Text content of the message.

Generation Parameters (Optional)

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Type	Default	Description
`temperature`	float	1.0	Controls randomness in output generation. Lower values produce more deterministic responses.
`top_p`	float	1.0	Nucleus sampling threshold—controls diversity by selecting from the top percentile of possible tokens.
`n`	int	1	Number of completions to generate for each input request.
`max_tokens`	int	null	Maximum number of tokens to generate in the response.
`stream`	boolean	false	If true, enables real-time streaming of response tokens using Server-Sent Events (SSE).

","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"SEEYOU_API_KEY"}]},"isInherited":true,"source":{"_postman_id":"1e1f34ea-7d2a-4024-b43a-b37cefdc8e14","id":"1e1f34ea-7d2a-4024-b43a-b37cefdc8e14","name":"SEEYOU API REFERENCE","type":"collection"}},"urlObject":{"protocol":"https","path":["api","v1","chat","completion"],"host":["api","seeyou","eu"],"query":[],"variable":[]}},"response":[{"id":"bb281fb5-02a2-4cbb-88f0-ba886108ca96","name":"OK","originalRequest":{"method":"POST","header":[{"key":"Content-Type","value":"application/json","type":"text"}],"url":"https://api.seeyou.eu/api/v1/chat/completion"},"code":200,"_postman_previewlanguage":"Text","header":[],"cookie":[],"responseTime":null,"body":"{\n \"thread_id\":\"thread_989879879807098098\",\n \"response\": \"What is AI?\nArtificial Intelligence (AI) is a branch of computer science focused on building systems that can perform tasks normally requiring human intelligence. These tasks include:\n\nLearning from data (Machine Learning)\nUnderstanding language (Natural Language Processing)\nPerception (Computer Vision, Speech Recognition)\nDecision-making (Expert Systems, Robotics)\nSome common examples:\n\nVirtual assistants like Siri or Alexa\nChatGPT (AI-powered chatbot)\nRecommendation systems (Netflix, Amazon)\nAutonomous vehicles\n🎯 How to Make a Career in AI\n1. Educational Foundation\n\nMath & Statistics – Linear Algebra, Calculus, Probability\nProgramming – Python is the most used language in AI\nAlgorithms & Data Structures\n2. Learn Key AI Technologies\n\nMachine Learning (scikit-learn, TensorFlow, PyTorch)\nDeep Learning (Neural Networks, CNNs, RNNs)\nNatural Language Processing (transformers, Hugging Face)\nComputer Vision (OpenCV, YOLO)\n3. Projects & Portfolio\n\nBuild and showcase projects:\n\nImage classifier\nChatbot using GPT\nSentiment analysis on tweets\nFace recognition system\nUse GitHub to display your work.\n\n4. Courses & Certifications\n\nDeepLearning.AI by Andrew Ng (Coursera)\nFast.ai\nGoogle’s ML Crash Course\n5. Tools & Frameworks\n\nPython, NumPy, Pandas\nTensorFlow, PyTorch\nJupyter Notebooks\nHuggingFace Transformers\nLangChain (for building LLM-based apps)\n6. Internships & Jobs\n\nStart with:\n\nIntern roles in data science / ML\nFreelance on AI tasks (Kaggle, Upwork)\nContribute to open-source AI projects\n7. Stay Updated\n\nFollow papers at arXiv.org\nJoin communities like Reddit r/MachineLearning, Discords, or AI conferences\n🧭 Career Paths in AI\nAI Researcher\nMachine Learning Engineer\nData Scientist\nAI Product Manager\nNLP Engineer\nComputer Vision Specialist\", \n \"source_files\": []\n}"}],"_postman_id":"ec174b66-de1d-4c5f-9d6d-311e881dd812"},{"name":"Stop","id":"735d310c-8d05-4fad-bbff-8b5edcb513c1","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer SEEYOU_API_KEY"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"thread_id\":\"thread_989879879807098098\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.seeyou.eu/api/v1/chat/stop","description":"

Chat Stop

The Chat Stop API endpoint is used to immediately terminate an active conversation. This can be useful in scenarios where the chat needs to be halted due to user request, system conditions, or moderation controls. Once invoked, the session is closed and no further messages will be processed or responded to.

Body Parameters

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Type	Description
`thread_id`	string (optional)	Unique identifier for maintaining conversation context across multiple requests. Omit to initiate a new, stateless interaction.

Chat History Update

The Chat History Update endpoint is responsible for updating the title of a conversation history using the corresponding threadId. This allows you to rename or customize the title of a chat thread for better organization, clarity, and future reference

Request Format

Authentication Header

Authorization: Bearer SEEYOU_API_KEY\nContent-Type: application/json\n\n

Body Parameters

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Type	Description
`title`	string	You can specify a title for each conversation.
`thread_id`	string	To update the title of a conversation, you must pass the corresponding thread_id in the request. The thread_id uniquely identifies the specific chat thread whose title you want to modify

Chat History

The Chat History API endpoint is responsible for retrieving the complete message history associated with a specific thread ID. It returns user and messages exchanged within that conversation thread, preserving the context and flow of the dialogue. This allows applications to maintain conversational continuity, display past interactions to users, and support features like follow-up questions & show history of messages.

Request Format

Authentication Header

Authorization: Bearer SEEYOU_API_KEY\nContent-Type: application/json\n\n

Query Parameters

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Type	Description
`size`	integer (optional)	You can specify a size value between 1 and 100, which determines the number of results to be returned in a single API response. This parameter is useful for controlling pagination and optimizing performance by limiting the volume of data retrieved at once. For example, setting size=10 will return the first 10 records, while size=100 will return the maximum allowed per request.
`search`	string (optional)	You can use the search key to filter history based on message keywords. This allows you to quickly find specific conversations or topics by matching user or messages that contain the given keyword or phrase. It’s especially useful for locating past queries, identifying patterns in user interactions, or retrieving relevant message threads without manually browsing the entire history.

Chat History Delete

The Chat History Delete API endpoint is responsible for deleting conversation history associated with a specific thread_id. When a user wants to remove a particular chat thread—either for privacy, cleanup, or data management purposes—this endpoint allows them to permanently delete all messages within that conversation.

Request Format

Authentication Header

Authorization: Bearer SEEYOU_API_KEY\nContent-Type: application/json\n\n

Query Parameters

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Type	Description
`thread_id`	string	To delete a message conversation, you must include the corresponding thread_id in the request. The thread_id uniquely identifies the specific chat thread that should be deleted, ensuring that only the intended conversation is removed.

Files Upload

The Upload Files endpoint allows you to upload multiple files at once to the SEEYOU platform. These uploaded files are securely stored and can be used later in document-based chat completions, AI-powered search, or custom processing workflows.

Request Format

Authentication Header

Authorization: Bearer SEEYOU_API_KEY\nContent-Type: application/json\n\n

Body Parameters (form-data)

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Type	Description
`files[]`	file, required	The files to be uploaded in bulk. Supported formats include .pdf, .docx, .txt, and other commonly used document formats. You can upload multiple files in a single request, making it easier to process batches of documents for parsing, and vectorization.

Files List

The Files List endpoint allows you to retrieves a list of files from the API response with pagination.

Query Parameters

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Type	Description
`page`	number, required	The page number of results to retrieve. Used for pagination to navigate through large sets of data.
`size`	number, optional	The number of items to return per page(Max: 100). Defaults 10 results will come in every request.
`order`	string, optional	The sorting order of the results is apply on created_at column. You can use asc for ascending and desc for descending.
`search`	string, optional	A search query string used to filter results based on matching text in one or more fields.

Files Retrieve

The Retrieve Files endpoint allows you to fetche the details and contents of a specific file using its unique identifier.

Path Parameters

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Type	Description
`file_id`	string, required	file_id is a unique identifier for the file, used to retrieve or reference a specific file within the system.

Files Delete

The Delete Files endpoint allows to deletes a specific file from the system using its unique file ID.

Path Parameters

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Field	Type	Description
`file_id`	string, required	file_id is a unique identifier for the file, used to retrieve or reference a specific file within the system.