> ## Documentation Index > Fetch the complete documentation index at: https://docs.lukittu.com/llms.txt > Use this file to discover all available pages before exploring further. # Delete License by Key > Delete a license by its license key. **This operation is permanent and cannot be undone.** ## OpenAPI ````yaml /api-reference/openapi.json delete /api/v1/dev/teams/{teamId}/licenses/{licenseKey} openapi: 3.0.1 info: title: Lukittu API description: > The Lukittu API provides comprehensive license management and verification services for software products. ## Authentication **Client Endpoints** (`/api/v1/client/*`): No authentication required. These are public endpoints for license verification. **Developer Endpoints** (`/api/v1/dev/*`): Require API key authentication via Bearer token. ## API Types - **Client API**: Used by your software to verify licenses, send heartbeats, and download releases - **Developer API**: Used for programmatic license management from your backend systems ## Rate Limiting All endpoints are rate-limited to prevent abuse. If you exceed the rate limit, you'll receive a 429 status code. ## Response Format All responses follow a consistent format with `data` and `result` objects: ```json { "data": {}, // Response data (null for errors) "result": { "timestamp": "2023-09-15T14:30:00Z", "valid": true, "details": "Human-readable message", "code": "SUCCESS_CODE" // Optional error/success code } } ``` version: 1.0.0 contact: name: Lukittu Community url: https://discord.lukittu.com servers: - url: https://app.lukittu.com description: Production server security: [] tags: - name: Client - Verify description: > Client endpoints for license verification, heartbeat monitoring, and file downloads. These endpoints are used directly by your software applications. - name: Dev - Licenses description: | Developer endpoints for license management operations. These endpoints require API key authentication. - name: Dev - Customers description: | Developer endpoints for customer management operations. These endpoints require API key authentication. - name: Dev - Releases description: | Developer endpoints for release management operations. These endpoints require API key authentication. - name: Dev - Statistics description: | Developer endpoints for retrieving team usage statistics. These endpoints require API key authentication. paths: /api/v1/dev/teams/{teamId}/licenses/{licenseKey}: delete: tags: - Dev - Licenses summary: Delete License by Key description: | Delete a license by its license key. **This operation is permanent and cannot be undone.** operationId: deleteLicenseByKey parameters: - $ref: '#/components/parameters/TeamId' - $ref: '#/components/parameters/LicenseKeyPath' responses: '200': description: License successfully deleted content: application/json: schema: $ref: '#/components/schemas/LicenseDeletionResponse' example: data: licenseKey: ABCD1-EFGH2-IJKL3-MNOP4-QRST5 deleted: true result: timestamp: '2023-09-15T14:30:00Z' valid: true details: License deleted successfully 4XX: $ref: '#/components/responses/StandardError' 5XX: $ref: '#/components/responses/StandardError' security: - bearerAuth: [] components: parameters: TeamId: name: teamId in: path required: true description: >- Your team's UUID. You can find this value in your team's settings on the Lukittu dashboard. schema: $ref: '#/components/schemas/UUID' example: 123e4567-e89b-12d3-a456-426614174000 LicenseKeyPath: name: licenseKey in: path required: true description: The Lukittu license key to operate on. schema: $ref: '#/components/schemas/LicenseKey' example: ABCD1-EFGH2-IJKL3-MNOP4-QRST5 schemas: LicenseDeletionResponse: allOf: - $ref: '#/components/schemas/SuccessResponse' - type: object properties: data: type: object properties: licenseId: $ref: '#/components/schemas/UUID' description: ID of the deleted license licenseKey: $ref: '#/components/schemas/LicenseKey' description: Key of the deleted license deleted: type: boolean enum: - true description: Confirmation that license was deleted anyOf: - required: - licenseId - deleted - required: - licenseKey - deleted UUID: type: string format: uuid description: UUID v4 identifier LicenseKey: type: string pattern: ^[A-Z0-9]{5}-[A-Z0-9]{5}-[A-Z0-9]{5}-[A-Z0-9]{5}-[A-Z0-9]{5}$ description: >- Lukittu license key format: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX where X is an uppercase letter (A-Z) or digit (0-9) SuccessResponse: type: object properties: data: type: object description: Response data result: allOf: - $ref: '#/components/schemas/StandardResult' - type: object properties: valid: type: boolean enum: - true description: Always true for success responses required: - data - result ErrorResponse: type: object properties: data: type: object description: Additional error-related data nullable: true result: allOf: - $ref: '#/components/schemas/StandardResult' - type: object properties: valid: type: boolean enum: - false description: Always false for error responses code: type: string description: Error code indicating the specific issue enum: - INTERNAL_SERVER_ERROR - BAD_REQUEST - LICENSE_NOT_FOUND - IP_LIMIT_REACHED - HWID_LIMIT_REACHED - PRODUCT_NOT_FOUND - CUSTOMER_NOT_FOUND - LICENSE_EXPIRED - LICENSE_SUSPENDED - TEAM_NOT_FOUND - RATE_LIMIT - HARDWARE_IDENTIFIER_BLACKLISTED - COUNTRY_BLACKLISTED - IP_BLACKLISTED - RELEASE_NOT_FOUND - FORBIDDEN - UNAUTHORIZED - INVALID_SESSION_KEY - NO_ACCESS_TO_RELEASE - RELEASE_ARCHIVED - RELEASE_DRAFT required: - code required: - result StandardResult: type: object properties: timestamp: type: string format: date-time description: Timestamp when the response was generated valid: type: boolean description: Indicates whether the operation was successful details: type: string description: Human-readable description of the result required: - timestamp - valid - details responses: StandardError: description: > Standard API error response. All errors follow the same `{data, result}` structure. The HTTP status code indicates the general error category, while `result.code` provides specific error details. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: apiKey description: > API key authentication for development endpoints. You can create API keys in your team's settings on the Lukittu dashboard. Include the API key in the Authorization header as: `Bearer YOUR_API_KEY` Example: ``` Authorization: Bearer lukittu_api_key_abc123def456... ``` ````