> ## 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. # Add an attendee > Adds someone who came, like the Add button on the portal's sheet: the row is marked as arrived and the person joins your contacts. With `Idempotency-Key`, the same request within 10 minutes adds nothing more. Needs the `listings:write`, `leads:read` and `leads:write` abilities. ## OpenAPI ````yaml en/openapi.json POST /viewings/{slot}/attendees 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: /viewings/{slot}/attendees: post: tags: - Viewings summary: Add an attendee description: >- Adds someone who came, like the Add button on the portal's sheet: the row is marked as arrived and the person joins your contacts. With `Idempotency-Key`, the same request within 10 minutes adds nothing more. Needs the `listings:write`, `leads:read` and `leads:write` abilities. operationId: v1.open_house.attendees.store parameters: - name: slot in: path required: true schema: type: integer description: The id of the time or window, from the agenda's `slots[].id`. - name: Idempotency-Key in: header required: false schema: type: string description: >- A unique value for this creation (for example a UUID). A request repeated with the same value within 10 minutes returns what the first one created, without creating anything else: the listing for `POST /listings`, the contact for `POST /leads`, the message for `POST /leads/{lead}/messages`. For listings and messages, only the first 64 characters count. - 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. requestBody: required: true content: application/json: schema: type: object properties: name: type: string maxLength: 120 description: Name. phone: type: - string - 'null' pattern: ^\+?[0-9 ()\-]{6,32}$ maxLength: 32 description: Phone. required: - name responses: '200': content: application/json: schema: type: object properties: data: $ref: '#/components/schemas/OpenHouseAttendeeApiResource' description: The result of the request. required: - data description: The request succeeded. '201': content: application/json: schema: type: object properties: data: $ref: '#/components/schemas/OpenHouseAttendeeApiResource' description: The result of the request. required: - data description: The row that was added. '400': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: The request body is not valid JSON (`malformed_json`). '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`). '404': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: >- The listing does not exist or the key has no access to it (`not_found`). '409': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: >- The sheet refuses the action right now, for example outside the open house's window, with the reason in `detail` (`listing_action_refused`), or a request with the same `Idempotency-Key` is still in progress (`idempotency_key_in_use`). '413': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: The request body is larger than 1 MB (`payload_too_large`). '415': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: >- The request body isn't declared as JSON (`unsupported_media_type`). Send it with `Content-Type: application/json`. '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`. '503': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: >- Housera has temporarily paused writes through the API (`api_writes_paused`). Try again after the number of seconds in `Retry-After`. components: schemas: OpenHouseAttendeeApiResource: type: object properties: id: type: integer description: >- The event ID (ULID, increasing). Send it as `after` to continue where you left off. name: type: string description: Name. phone: type: - string - 'null' description: Phone. source: type: string description: >- Where the row comes from: `rsvp` (said they're coming on the listing page), `checkin` (signed at the door) or `manual` (added by you). account: type: boolean description: '`true` when the row is a Housera account''s.' rsvp_at: type: - string - 'null' description: When they said they're coming, or `null`. arrived_at: type: - string - 'null' description: When they arrived, or `null`. interested: type: boolean description: '`true` when you marked them as interested.' consent: type: boolean description: >- `true` when the person agreed to be contacted; only then does the row keep the phone written at the door. consent_at: type: - string - 'null' description: When they gave their consent, or `null`. consent_version: type: - string - 'null' description: The version of the notice they accepted, or `null`. required: - id - name - phone - source - account - rsvp_at - arrived_at - interested - consent - consent_at - consent_version title: OpenHouseAttendeeApiResource 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.