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

# Create pending attendee

> Creates a pending attendee record during form submission. This is temporary data that gets deleted when booking is completed.



## OpenAPI

````yaml /openapi.json post /v4/attendee/pending
openapi: 3.0.0
info:
  title: meetergo Platform API
  description: >-
    Scheduling, CRM and invoicing in one API: create users, manage availability
    and bookings, connect calendars, keep contacts and deals in sync, and take
    an offer through to a paid invoice.
  version: 3.274.0
  contact: {}
  termsOfService: https://www.meetergo.com/tos/
servers: []
security: []
tags:
  - name: User V4
    description: Create and manage users in your workspace
  - name: Meeting Type V4
    description: Configure meeting templates with durations, buffers, and conferencing
  - name: availability
    description: Manage weekly schedules and availability settings
  - name: Booking V4
    description: Create new bookings
  - name: Booking Availability V4
    description: Query available time slots for booking
  - name: Appointment V4
    description: Manage existing appointments
  - name: Attendee V4
    description: Manage attendee details and notes
  - name: Calendar Connections V4
    description: Connect and sync external calendars
  - name: Signatures V4
    description: >-
      Send PDFs for e-signature and download the signed, eIDAS-grade document
      (DocuSeal-compatible)
  - name: WhatsApp V4
    description: >-
      Send and receive WhatsApp messages by phone number and read conversation
      history
  - name: One Time Booking Link V4
    description: Create single-use booking links
  - name: availability-exception
    description: Override availability for specific dates
  - name: Booking Link V4
    description: Configure various booking page types
  - name: Personal Page V4
    description: Manage user profile pages
  - name: Handoff V4
    description: Reassign meetings to other hosts
  - name: Calendar Auth V4
    description: OAuth callbacks for calendar providers
  - name: CRM Contacts
    description: >-
      Create, find, and update the people in your CRM, including their custom
      data fields
  - name: CRM Deals
    description: >-
      Create, update, and track deals through pipeline stages (incl. per-deal
      activity history)
  - name: CRM Pipelines
    description: Manage pipelines and their stages
  - name: CRM Tasks
    description: Tasks on contacts, deals and companies
  - name: CRM Notes
    description: Notes on contacts, deals and companies
  - name: CRM Attachments
    description: Files attached to contacts, deals and companies
  - name: CRM Communications
    description: Logged calls, messages and meetings on contacts, deals and companies
  - name: CRM Email Sync
    description: Read the email history synced from connected mailboxes (read-only)
  - name: Data Fields
    description: >-
      Define the custom fields a contact can carry; their `name` is the key used
      in a contact's additionalData
  - name: Invoicing Documents
    description: >-
      Offers and invoices: create a draft, finalize it into a numbered
      e-invoice, send it, record payments, and run Mahnwesen
  - name: Invoicing Products
    description: Reusable products for invoice line items
  - name: Invoicing Settings
    description: Seller details, tax treatment, bank accounts, and number ranges
  - name: Invoicing Recurring
    description: >-
      Recurring schedules, billing runs over completed meetings, buyer prefill,
      and DATEV export
  - name: Queue V4
    description: Round-robin and queue-based routing (Beta)
  - name: Queue User Group V4
    description: Manage queue user groups (Beta)
  - name: Meeting Type Template V4
    description: Reusable meeting type configurations (Beta)
  - name: Attendee Pending V4
    description: Manage pending attendee approvals (Beta)
  - name: Provisional Booking V4
    description: Manage provisional/unconfirmed bookings (Beta)
paths:
  /v4/attendee/pending:
    post:
      tags:
        - Attendee Pending V4
      summary: Create pending attendee
      description: >-
        Creates a pending attendee record during form submission. This is
        temporary data that gets deleted when booking is completed.
      operationId: postInfo
      parameters: []
      requestBody:
        required: true
        description: Attendee information collected during form entry
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateAttendeePendingDto'
      responses:
        '201':
          description: Pending attendee created successfully
          content:
            application/json:
              schema:
                type: number
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '429':
          $ref: '#/components/responses/TooManyRequests'
components:
  schemas:
    CreateAttendeePendingDto:
      type: object
      properties:
        email:
          type: string
          description: |-
            Attendee email address. Required for all standard bookings.
            Optional only when `BookingDto.phoneOnlyBooking` is true.
            Validated as email format when provided.
          format: email
        firstname:
          type: string
          description: Either fullname or firstname/lastname is required
          maxLength: 150
        lastname:
          type: string
          description: Either fullname or firstname/lastname is required
          maxLength: 150
        fullname:
          type: string
          description: Either fullname or firstname/lastname is required
          maxLength: 150
        bringalongEmails:
          description: Additional attendee emails (max 5)
          maxItems: 5
          type: array
          items:
            type: string
            format: email
        notes:
          type: object
          description: An object containing attendee form entries.
          additionalProperties:
            type: string
        billingDetails:
          nullable: true
          description: >-
            Billing details from the booking page's billing block, shown when
            the

            meeting type sets `meetingPaymentInfo.collectBillingDetails`.
          allOf:
            - $ref: '#/components/schemas/BookingBillingDetailsDto'
        phone:
          type: string
        language:
          allOf:
            - $ref: '#/components/schemas/Language'
        timezone:
          type: string
        dataPolicyAccepted:
          type: boolean
        companyId:
          type: string
          format: uuid
      required:
        - notes
        - companyId
    BookingBillingDetailsDto:
      type: object
      properties:
        company:
          type: string
          maxLength: 255
        addressLine1:
          type: string
          maxLength: 255
        addressLine2:
          type: string
          maxLength: 255
        postalCode:
          type: string
          maxLength: 16
        city:
          type: string
          maxLength: 120
        countryCode:
          type: string
          description: ISO 3166-1 alpha-2
          maxLength: 2
        vatId:
          type: string
          description: USt-IdNr.
          maxLength: 32
    Language:
      type: string
      enum:
        - en
        - de
        - fr
        - es
        - 'no'
        - nl
        - it
        - pl
        - se
        - tr
        - da
    ApiError:
      type: object
      required:
        - statusCode
        - message
      properties:
        statusCode:
          type: integer
          example: 400
        message:
          oneOf:
            - type: string
            - type: array
              items:
                type: string
          description: >-
            A sentence, or the list of field constraints that failed. Validation
            errors name the offending property.
          example:
            - limit must not be greater than 100
        error:
          type: string
          example: BadRequestException
  responses:
    BadRequest:
      description: >-
        The request did not validate. `message` lists the constraints that
        failed.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
    Unauthorized:
      description: Missing, malformed, or expired credentials.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
    Forbidden:
      description: >-
        Authenticated, but not allowed: the plan does not include this feature,
        or the token is scoped away from it.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
    TooManyRequests:
      description: Rate limited. Back off and retry.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'

````

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