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

# Delete meeting place

> Delete a meeting place for a scheduling link.

<Warning>This endpoint is part of API v1, which is deprecated. Please use the [v2 API](/getting-started/introduction) instead.</Warning>

<Info>Replace `{your-subdomain}` with your workspace’s subdomain. <br /> Learn how to find your subdomain in [Workspace subdomain](/getting-started/workspace-subdomain).</Info>


## OpenAPI

````yaml bundled-v1/spots.yaml DELETE /meetings/{meeting_sid}/spots/{id}
openapi: 3.0.3
info:
  title: NeetoCal Meeting Places APIs
  version: 1.0.0
servers:
  - description: NeetoCal APIs
    url: https://{your-subdomain}.neetocal.com/api/external/v1
    variables:
      your-subdomain:
        default: spinkart
        description: >-
          Replace **spinkart** with your [workspace's
          subdomain](/getting-started/workspace-subdomain).
security: []
tags:
  - name: Meeting Spots
    description: >-
      APIs to manage meeting locations and platforms (spots) for scheduling
      links.
paths:
  /meetings/{meeting_sid}/spots/{id}:
    delete:
      tags:
        - Meeting Spots
      summary: Delete a spot
      description: Delete a meeting place for a scheduling link.
      parameters:
        - $ref: '#/components/parameters/api_key_header'
        - in: path
          name: meeting_sid
          description: >
            The unique identifier (SID) of the scheduling link you want to use.
            You can get `sid` in different ways. Visit the scheduling link page
            and then click on "Settings" > "Show SID". That will give you `sid`.
            You can also get this from the response of the [List scheduling
            links](/api-reference/scheduling-links/list) endpoint, where it
            appears as the `sid` property for each scheduling link in the
            response.
          required: true
          schema:
            type: string
            example: vj5pgkh
        - in: path
          name: id
          description: >
            The unique identifier of the place. You can get this `id` from the
            response of the [List meeting
            places](/api-reference/meeting-places/list) endpoint, where it
            appears as the `id` property for each place in the response.
          required: true
          schema:
            type: string
            example: 1d35e633-71b9-4ad9-b659-b034f361539b
      responses:
        '200':
          description: OK - Request succeeded
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    example: Spot destroyed successfully
components:
  parameters:
    api_key_header:
      in: header
      name: X-Api-Key
      description: >-
        Use the X-Api-Key header to provide your workspace API key. Refer to
        [Authentication](/getting-started/authentication) for more information.
      required: true
      schema:
        type: string

````