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

# Burn NFT

> Burn a minted NFT.

**API scope required**: `nfts.delete`


<Snippet file="alpha-api-note.mdx" />


## OpenAPI

````yaml delete /2022-06-09/collections/{collectionId}/nfts/{id}
openapi: 3.0.1
info:
  description: N/A
  version: 1.0.0
  title: NFT Minting
  contact:
    name: Crossmint NFT Minting APIs
    url: https://www.crossmint.com
    email: support@crossmint.com
servers:
  - url: https://staging.crossmint.com/api
    description: Staging environment (testnets)
  - url: https://www.crossmint.com/api
    description: Production environment (mainnets)
security:
  - apiKey: []
paths:
  /2022-06-09/collections/{collectionId}/nfts/{id}:
    delete:
      tags:
        - NFTs
      summary: Burn NFT
      description: |
        Burn a minted NFT.

        **API scope required**: `nfts.delete`
      operationId: burn-nft
      parameters:
        - $ref: '#/components/parameters/collectionId'
        - $ref: '#/components/parameters/nftId'
      responses:
        '200':
          description: Success.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BurnNFTResponse'
        '400':
          description: >-
            Invalid arguments, please make sure you're following the api
            specification.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/400Response'
        '403':
          description: Forbidden error, please ensure the credentials are correct.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/403Response'
        '404':
          description: Not found error.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/404Response'
        '503':
          description: >-
            Please try again in a few minutes. If the issue still persists,
            contact Crossmint support.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/503Response'
components:
  parameters:
    collectionId:
      name: collectionId
      in: path
      description: >
        This is the identifier for the collection related to the request. Every
        project has default collections: `default-solana` and
        `default-polygon`. 


        The
        [create-collection](/api-reference/minting/collection/create-collection)
        API will result in collections with UUID formatted `collectionId`. 

        **Example:** `9c82ef99-617f-497d-9abb-fd355291681b`


        The
        [create-collection-idempotent](/api-reference/minting/collection/create-collection-idempotent)
        API allows you to specify an arbitrary identifier during the initial
        request.

        **Example:** `your-custom-identifier`
      required: true
      example: default-solana
      schema:
        type: string
    nftId:
      name: id
      in: path
      description: Unique ID of the minted NFT returned in the mint response
      required: true
      schema:
        type: string
  schemas:
    BurnNFTResponse:
      type: object
      properties:
        actionId:
          type: string
          description: >
            Can be used to check the status via the [action status
            API](/api-reference/common/get-action-status)
          example: 201520fc-e0eb-4698-a2f3-c6b50cc7c894
        action:
          type: string
          description: The action performed, in this case `nfts.delete`
          example: nfts.delete
        status:
          type: string
          description: >-
            Current status of the async operation. One of `pending` or
            `succeeded`
          example: pending OR succeeded
        data:
          type: object
          properties:
            chain:
              type: string
              description: >-
                Refer to the [supported chains](/introduction/supported-chains)
                page for more info
              example: polygon
            txId:
              type: string
              description: |
                The onchain transaction ID related to the request. 

                This is only present when `status` is `succeeded`
              example: >-
                succeeded status ONLY -
                0x69cf6d971e6745f25f683db9c87663839be02bdaa4a70f0724f490d7335b0081
            collection:
              type: object
              properties:
                id:
                  type: string
                  description: >-
                    The Crossmint identifier for the collection. Either a UUID
                    or custom string depending on how you create the collection.
                  example: default-polygon
                contractAddress:
                  type: string
                  description: The onchain contract address for the given collection.
                  example: '0x67a602CBb306b3DBaaC7ECf55b72EED0E04Dc785'
            token:
              type: object
              properties:
                id:
                  type: string
                  description: The Crossmint identifier for the NFT. This will be a UUID.
                  example: 799a6f68-e2ea-4126-8577-4298dfcf900c
                tokenId:
                  type: string
                  description: The numeric tokenId of the NFT in the contract.
                  example: '7'
        startedAt:
          type: string
          format: date-time
          description: The time this operation was initiated in UTC.
          example: '2024-01-10T23:01:45.000Z'
        completedAt:
          type: string
          format: date-time
          description: |
            The time this operation completed in UTC.

            This is only present when `status` is `succeeded`
          example: succeeded status ONLY - 2024-01-10T23:02:00.000Z
        resource:
          type: string
          description: >-
            The URL path to obtain current status with [action status
            api](/api-reference/common/get-action-status)
          example: >-
            https://staging.crossmint.com/api/2022-06-09/collections/default-polygon/nfts/201520fc-e0eb-4698-a2f3-c6b50cc7c894
    400Response:
      type: object
      properties:
        error:
          type: boolean
          example: true
        message:
          type: string
          example: Invalid arguments or empty parameter <missing parameter>.
    403Response:
      type: object
      properties:
        error:
          type: boolean
          example: true
        message:
          type: string
          example: Malformed API key. / API key provided doesn't have required scopes.
    404Response:
      type: object
      properties:
        error:
          type: boolean
          example: true
        message:
          type: string
          example: Not found
    503Response:
      type: object
      properties:
        error:
          type: boolean
          example: true
        message:
          type: string
          example: >-
            Please try again in a few minutes. If the issue still persists,
            contact Crossmint support.
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: X-API-KEY
      description: Obtained in the Crossmint developer console

````