> ## Documentation Index
> Fetch the complete documentation index at: https://developers.vizito.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Anonymising a visit

> Strips every personal detail from a visit, irreversibly. What remains is
the shape of the visit — id, visit type, entry point, host, sign-in and
sign-out times, and `erased: true`. The photo and signature are deleted
outright and the first name becomes `Anonimized`.

There is no undo. Routine cleanup does not need this endpoint: data
retention deletes old visits on its own schedule.




## OpenAPI

````yaml https://vizito.eu/openapi.yaml put /visitors/{visitor_id}/anonymize
openapi: 3.1.0
info:
  title: Vizito API
  version: 1.0.0
  description: |
    Read and write your Vizito visitor data over HTTPS.

    Every endpoint takes and returns JSON, and is authenticated with an API key
    created by a global admin on the Integrations page of the Backoffice.

    Almost every endpoint names a **location** — `company_id` in the API. Your
    key is pinned to a set of locations; naming one outside that set is refused
    with `403`. Start at `GET /companiesList`, the one endpoint that needs no
    location id.
  contact:
    name: Vizito support
    email: support@vizito.eu
    url: https://vizito.eu
  termsOfService: https://vizito.eu/terms
servers:
  - url: https://api.vizito.eu/api
    description: Production
security:
  - apiKey: []
tags:
  - name: Locations
    description: The locations your credential covers, and their configuration.
  - name: Visitors
    description: The visits themselves — one visitor is one visit, not a person.
  - name: Registered visitors
    description: Expected visitors — pre-register, invite, and sign in on arrival.
  - name: Hosts
    description: The people who can be visited.
  - name: Visit types
    description: The sign-in flows, and the questions they ask.
  - name: Entry points
    description: The doors and desks within a location.
  - name: Agreements
    description: The documents visitors sign, and the signed PDFs that come out.
  - name: Devices
    description: The kiosks at a location.
  - name: Reporting
    description: Counters, graphs and exports.
  - name: Webhooks
    description: The endpoint Vizito calls when something happens.
paths:
  /visitors/{visitor_id}/anonymize:
    put:
      tags:
        - Visitors
      summary: Anonymising a visit
      description: |
        Strips every personal detail from a visit, irreversibly. What remains is
        the shape of the visit — id, visit type, entry point, host, sign-in and
        sign-out times, and `erased: true`. The photo and signature are deleted
        outright and the first name becomes `Anonimized`.

        There is no undo. Routine cleanup does not need this endpoint: data
        retention deletes old visits on its own schedule.
      operationId: anonymiseVisit
      parameters:
        - name: visitor_id
          in: path
          required: true
          description: The visit id.
          schema:
            $ref: '#/components/schemas/ObjectId'
      responses:
        '200':
          description: The visit was anonymised.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Message'
        '400':
          $ref: '#/components/responses/BadRequest'
        '403':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    ObjectId:
      type: string
      pattern: ^[0-9a-fA-F]{24}$
      description: A 24-character hexadecimal id.
      example: 5f2a1b9c4d3e2f0011223344
    Message:
      type: object
      properties:
        message:
          type: string
  responses:
    BadRequest:
      description: The request was understood but could not be carried out.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Message'
    Unauthorized:
      description: |
        The credential was refused, or the endpoint is off limits to API keys.
        Every refusal answers identically — see the Authentication page.
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: string
                example: Invalid API key
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      description: >
        An API key issued in the Backoffice, sent as `Authorization: Bearer
        vzk_<key id>_<secret>`.

        A Microsoft Entra ID access token obtained with the client credentials

        grant is accepted on the same header. The same value is also accepted in

        an `X-API-Key` header.

````

## Related topics

- [Signing a visitor in and out](/documentation/signing-in-a-visitor.md)
- [Updating a visit](/api-reference/visitors/updating-a-visit.md)
- [Fetching a visit type](/api-reference/visit-types/fetching-a-visit-type.md)
- [Listing visit types](/api-reference/visit-types/listing-visit-types.md)
- [Listing recent visits](/api-reference/visitors/listing-recent-visits.md)