> ## 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. # The team > The people on the team, as on the portal's Team page, in the order they joined the company, with cursor pagination: their public name, role, office, projects at a developer and whether they work now. The owner and admins see the whole team, a manager the people of their office, and an agent the whole team, but only their own email and phone. While the company is suspended, the list is empty. Requires the `listings:read` permission. ## OpenAPI ````yaml en/openapi.json GET /account/members 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/members: get: tags: - The company and its team summary: The team description: >- The people on the team, as on the portal's Team page, in the order they joined the company, with cursor pagination: their public name, role, office, projects at a developer and whether they work now. The owner and admins see the whole team, a manager the people of their office, and an agent the whole team, but only their own email and phone. While the company is suspended, the list is empty. Requires the `listings:read` permission. operationId: v1.firm.members parameters: - 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/MemberApiResource' 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: MemberApiResource: type: object properties: id: type: integer description: >- The colleague's id on the team, the same as in the `member.*` events. name: type: string description: >- The colleague's approved public name, as on the company's page; without an approved name, the name on the team. email: type: - string - 'null' description: >- The colleague's email. `null` when you do not see it in the portal either: an agent sees only their own. phone: type: - string - 'null' description: >- The colleague's phone, in international format. `null` when you do not see it in the portal either. role: type: - string - 'null' description: >- `owner`, `admin`, `manager` or `agent`; `null` for a colleague who came from a CRM and has no account. position: type: - string - 'null' description: >- The colleague's job title, as the company wrote it; `null` if missing. office: type: - object - 'null' properties: id: type: integer description: The office's id. Send it as `office` in `GET /leads`. name: type: string description: >- The office's name. The head office is named in the language of the response: “Head office” in English, “Sediu” in Romanian. required: - id - name description: The colleague's office; `null` if they have none. projects: type: array items: type: string description: >- At a developer: the codes of the developments the colleague works on. The owner and admins work on all of them, and their list is empty. active: type: boolean description: >- `false` for a deactivated colleague: they stay on the team, with no access and no new requests. has_account: type: boolean description: >- `false` for a colleague who came from a CRM and has not made an account yet. joined_at: type: - string - 'null' description: When they joined the company (ISO 8601). required: - id - name - email - phone - role - position - office - projects - active - has_account - joined_at title: MemberApiResource 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.