> ## Documentation Index > Fetch the complete documentation index at: https://api.housera.ro/llms.txt > Use this file to discover all available pages before exploring further. # Read the messages from the Housera team > The messages the Housera team sent you in the official conversations, about a listing or about the account, and your replies, oldest first, with cursor pagination. With `after` you get only the messages after one you already have. Each message has its conversation (`conversation_id`) and the listing it is about (`listing`, `null` when it is about the account). You reply from the portal. A new message also comes as the `account.team_message` event. Requires the `listings:read` permission. ## OpenAPI ````yaml en/openapi.json GET /account/team-messages openapi: 3.1.2 info: title: Housera API version: 1.0.0 description: >- Publish and manage real estate listings on Housera from your CRM or your own application, under the same rules as the form on the Housera portal. servers: - url: https://staging.housera.ro/api/v1 description: 'Sandbox (staging): test data, same rules as production.' - url: https://housera.ro/api/v1 description: 'Production: the real listings on housera.ro.' security: - bearer: [] tags: - name: Your listings - name: Photos - name: Events - name: Vocabulary - name: Connect with Housera - name: Client requests - name: The company and its team - name: Marketing mandates - name: Viewings - name: Projects - name: Partnerships - name: API key - name: Statistics paths: /account/team-messages: get: tags: - Your listings summary: Read the messages from the Housera team description: >- The messages the Housera team sent you in the official conversations, about a listing or about the account, and your replies, oldest first, with cursor pagination. With `after` you get only the messages after one you already have. Each message has its conversation (`conversation_id`) and the listing it is about (`listing`, `null` when it is about the account). You reply from the portal. A new message also comes as the `account.team_message` event. Requires the `listings:read` permission. operationId: v1.team_messages.index parameters: - name: after in: query schema: type: - integer - 'null' minimum: 0 description: >- The cursor: the ID of the last event you have. You get only the events after it, in order. - name: per_page in: query schema: type: - integer - 'null' minimum: 1 maximum: 100 description: Results per page (default 50, maximum 100). - name: cursor in: query schema: type: - string - 'null' description: >- The next page's cursor, from `meta.next_cursor`, sent exactly as you received it. Any other value gets 422 (`pagination_cursor`). - name: locale in: query required: false schema: type: string enum: - ro - en default: en example: en description: >- The response language, `ro` or `en`. It changes error messages (`title`, `detail`), labels and, when the listing has an approved translation in that language, its title and description. Codes are the same in every language. It takes precedence over `Accept-Language` and over the account's language. responses: '200': content: application/json: schema: type: object properties: data: type: array items: $ref: '#/components/schemas/TeamMessageApiResource' description: The result of the request. links: type: object properties: first: type: - string - 'null' description: The first page's URL. last: type: - string - 'null' description: The last page's URL (null with cursor pagination). prev: type: - string - 'null' description: The previous page's URL, or null. next: type: - string - 'null' description: >- The next page: its URL, or the cursor to pass on. Null when there is nothing left. required: - first - last - prev - next description: Pagination links. meta: type: object properties: path: type: - string - 'null' description: The list's base URL. per_page: type: integer minimum: 0 description: Results per page. next_cursor: type: - string - 'null' description: The next page's cursor; null when the list has ended. prev_cursor: type: - string - 'null' description: The previous page's cursor; null on the first page. required: - path - per_page - next_cursor - prev_cursor description: >- Data about the response, outside the result, for example a list's pagination. required: - data - links - meta description: The request succeeded. '401': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: The key is missing, revoked or expired (`unauthenticated`). '403': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: >- The key lacks the required permission (`missing_ability`) or access is denied (`forbidden`). '422': content: application/problem+json: schema: $ref: '#/components/schemas/ValidationProblem' description: >- The data fails the rules: one entry per field in `errors[]`, each with a stable `code`. '429': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: >- Too many requests. Try again after the number of seconds in `Retry-After`. components: schemas: TeamMessageApiResource: type: object properties: conversation_id: type: integer description: >- The id of the official conversation the message belongs to. The `account.team_message` event carries the same id. listing: type: - string - 'null' description: >- The code of the listing the conversation is about, or `null` when it is about your account. id: type: integer description: >- The event ID (ULID, increasing). Send it as `after` to continue where you left off. direction: type: string enum: - out - in description: >- `in` for a message from the client, `out` for one sent from the listing's side (by you or by a colleague who handled the listing before). author: type: - object - 'null' properties: name: type: string description: Name. required: - name description: >- Who wrote the message, with the name as the portal's conversation shows it. body: type: - string - 'null' description: Message. kind: type: - string - 'null' enum: - viewing_request - null description: Type. deleted: type: boolean description: >- `true` when the author deleted the message. The message keeps its place, with no text. edited_at: type: - string - 'null' description: >- When the message was last edited (ISO 8601), `null` if it was never edited. read_at: type: - string - 'null' description: >- When the other side read the message (ISO 8601), `null` until they read it. created_at: type: - string - 'null' description: When the event happened (ISO 8601, UTC). required: - conversation_id - listing - id - direction - author - body - kind - deleted - edited_at - read_at - created_at title: TeamMessageApiResource Problem: type: object title: Problem properties: type: type: string format: uri description: The URL of the problem type (RFC 9457). title: type: string description: A short summary of the problem, in the request's language. status: type: integer description: The HTTP status code. code: type: string description: >- The stable code of the refusal, the one to handle the error by (the list is on the Errors page). detail: type: string description: The explanation, in the request's language. existing: type: object properties: code: type: string description: The existing listing's public code. external_ref: type: - string - 'null' description: >- Your ID for the existing listing, if you set it with `PUT /listings/ref/{ref}`. Otherwise `null`. required: - code - external_ref description: >- Only on `409 duplicate_listing`: the listing you already have for the same property. required: - type - title - status - code - detail ValidationProblem: type: object title: ValidationProblem properties: type: type: string format: uri description: The URL of the problem type (RFC 9457). title: type: string description: A short summary of the problem, in the request's language. status: type: integer description: 'The HTTP status code: `422`.' errors: type: array items: type: object properties: pointer: type: string description: The field it refers to, as a JSON Pointer (`/features/2`). code: type: string description: >- The rule that failed, as a stable code (the list is on the Errors page). detail: type: string description: >- The explanation, in the request's language. The wording can change, so handle the error by `code`. required: - pointer - code - detail description: One entry for each field that fails the rules. required: - type - title - status - errors securitySchemes: bearer: type: http scheme: bearer description: 'Authorization: Bearer ' ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.