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

# Check In Attendee to Event

> **Tool name:** `v1_checkin_event_attendee` · **Behaviour:** ✏️ Write

Record an event check-in for the attendee identified by a scanned QR code (raw code or Zuddl deep-link URL). Intended for onsite check-in partners pushing real-time scans back into Zuddl. If the scanned user is also a speaker for this event, the check-in is recorded against the speaker record.

**Same as Public API:** [Record an event check-in](/api-reference/attendees/record-an-event-check-in) (`POST /v1/events/{eventId}/attendees/attendance/checkin`)



## OpenAPI

````yaml https://api.prod.zuddl.com/api/v3/api-docs/mcp-tools post /tools/v1_checkin_event_attendee
openapi: 3.1.0
info:
  title: Zuddl MCP Tools Reference
  description: >-
    The Zuddl MCP server lets AI assistants such as Claude and ChatGPT work with
    your Zuddl organization through the [Model Context
    Protocol](https://modelcontextprotocol.io). This reference lists every tool
    the server offers. It is generated from the live server, so it always
    matches what your assistant sees.


    # Connecting


    Add `https://setup.zuddl.com/api/mcp` as a remote MCP server in your
    assistant. It signs you in to Zuddl with OAuth and then calls tools on your
    behalf, with your permissions. AI features must be enabled for your
    organization.


    # Calling a tool


    Assistants call a tool with a JSON-RPC `tools/call` request whose `name` is
    the tool name and whose `arguments` match the request body documented on the
    tool's page. The `/tools/<name>` paths in this reference identify tools;
    they are not HTTP endpoints.


    # Behaviour labels


    | Label | Meaning |

    | --- | --- |

    | 🔒 Read-only | Reads data and changes nothing. |

    | ✏️ Write | Creates or updates data, but does not delete it. |

    | ⚠️ Destructive | Deletes or removes data. Most assistants ask you to
    approve these calls. |

    | 🔁 Idempotent | Calling it again with the same arguments has no further
    effect. |


    A tool that mirrors a Public API endpoint links to that endpoint's page.
    MCP-only tools have no Public API equivalent.
  version: 1.0.0
servers:
  - url: https://setup.zuddl.com/api/mcp
    description: Zuddl MCP server
security:
  - oauth: []
tags:
  - name: Events
  - name: Attendees
  - name: Sessions
  - name: Speakers
  - name: Sponsors
  - name: Locations
  - name: Teams
  - name: Brand Kits
  - name: Registration flows & tickets
  - name: Analytics
paths:
  /tools/v1_checkin_event_attendee:
    post:
      tags:
        - Attendees
      summary: Check In Attendee to Event
      description: >-
        **Tool name:** `v1_checkin_event_attendee` · **Behaviour:** ✏️ Write


        Record an event check-in for the attendee identified by a scanned QR
        code (raw code or Zuddl deep-link URL). Intended for onsite check-in
        partners pushing real-time scans back into Zuddl. If the scanned user is
        also a speaker for this event, the check-in is recorded against the
        speaker record.


        **Same as Public API:** [Record an event
        check-in](/api-reference/attendees/record-an-event-check-in) (`POST
        /v1/events/{eventId}/attendees/attendance/checkin`)
      operationId: v1_checkin_event_attendee
      requestBody:
        description: The tool's `arguments`, as sent in a JSON-RPC `tools/call` request.
        content:
          application/json:
            schema:
              type: object
              properties:
                eventId:
                  type: string
                  description: Unique identifier of the event
                request:
                  type: object
                  description: >-
                    QR code identifying the attendee (raw code or Zuddl
                    deep-link URL) and optional scan timestamp
                  properties:
                    occurredAt:
                      type: string
                      format: date-time
                      description: >-
                        ISO-8601 timestamp of the scan from the partner's
                        device. Defaults to the server time when omitted.
                    qrCode:
                      type: string
                      description: >-
                        QR code identifying the attendee. Accepts either the raw
                        code (e.g. "EAFPSNAB2I") or a Zuddl deep-link URL such
                        as
                        "https://applink.zuddl.com/link/com.zuddl.portal/{eventId}/profile/{qrCode}"
                        — the server extracts the trailing path segment when a
                        URL is supplied.
                  required:
                    - qrCode
              required:
                - eventId
                - request
        required: true
      responses:
        '200':
          description: A JSON-RPC `tools/call` result. The tool's output is in `content`.
components:
  securitySchemes:
    oauth:
      type: http
      description: >-
        OAuth 2.1 access token. MCP clients obtain it themselves (dynamic client
        registration + PKCE) when you connect them to the server URL above.
      scheme: bearer

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.