# Convert Visitor Request Payload

Schema: #/components/schemas/convert_visitor_request

Method: SCHEMA
Version: 2.7
Security: bearerAuth

## Schema fields:

  - `type` (string, required)
    Represents the role of the Contact model. Accepts `lead` or `user`.
    Example: user

  - `user` (object, required)
    The unique identifiers retained after converting or merging.

  - `user.id` (string)
    The unique identifier for the contact which is given by Intercom.
    Example: 8a88a590-e1c3-41e2-a502-e0649dbf721c

  - `user.user_id` (string)
    A unique identifier for the contact which is given to Intercom, which will be represented as external_id.
    Example: 8a88a590-e1c3-41e2-a502-e0649dbf721c

  - `user.email` (string)
    The contact's email, retained by default if one is present.
    Example: joe@example.com

  - `visitor` (object, required)
    The unique identifiers to convert a single Visitor.

  - `visitor.id` (string)
    The unique identifier for the contact which is given by Intercom.
    Example: 8a88a590-e1c3-41e2-a502-e0649dbf721c

  - `visitor.user_id` (string)
    A unique identifier for the contact which is given to Intercom.
    Example: 8a88a590-e1c3-41e2-a502-e0649dbf721c

  - `visitor.email` (string)
    The visitor's email.
    Example: joe@example.com

