> ## Documentation Index > Fetch the complete documentation index at: https://docs.tightknit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Delete a composition > Deletes a composition that has no owner, such as one an API key created, with its versions, deliveries and comments; a scheduled send is canceled with it. A composition a Studio user owns stays theirs to delete, so it is a 403, as is one shared as `viewer` or `commenter`. Once sent, or while it is sending, it stays on record and is refused with a 400. This cannot be undone. ## OpenAPI ````yaml /openapi-v1.json delete /v1/compositions/{composition_id} openapi: 3.1.0 info: title: Tightknit Admin API version: 1.0.0 description: Administrative access to a Tightknit community. servers: - url: https://api.tightknit.ai security: - Bearer: [] tags: - name: API keys description: Inspect the key a request authenticated with. - name: Awards description: Badges and certificates a community grants its members. - name: Events description: Read, create, update and delete events on the community calendar. - name: Journeys description: Read multi-step member programs and their milestones. - name: Tags description: The labels that classify events and content resources. - name: Groups description: The segments a community sorts its members into. - name: Content description: >- The collections a community files its content under, and the links and events in them. - name: Feeds description: The Slack channels and site-only spaces a community posts in. - name: Files description: Images and documents a community has uploaded. - name: Messages description: What a community has published. - name: Members description: The people in a community. - name: Slack messages description: >- Messages sent to Slack. Sending is the only operation: they cannot be read, edited or deleted here. - name: Compositions description: >- Message Blaster drafts: messages saved in Studio before, and kept after, they are sent to Slack channels and members. An API key sees only the compositions shared with every Studio user. - name: Follows description: What a member follows. - name: Polls description: The questions a community puts to its members in Slack. - name: Activity logs description: What members did in the community, and when. - name: System description: Service health. paths: /v1/compositions/{composition_id}: delete: tags: - Compositions summary: Delete a composition description: >- Deletes a composition that has no owner, such as one an API key created, with its versions, deliveries and comments; a scheduled send is canceled with it. A composition a Studio user owns stays theirs to delete, so it is a 403, as is one shared as `viewer` or `commenter`. Once sent, or while it is sending, it stays on record and is refused with a 400. This cannot be undone. operationId: deleteComposition parameters: - schema: type: string pattern: ^cmps_[a-zA-Z0-9]{12}$ description: The composition's id. required: true description: The composition's id. name: composition_id in: path responses: '200': description: Success headers: Request-Id: description: Identifier for this request, quote it in support tickets. schema: type: string content: application/json: schema: $ref: '#/components/schemas/DeletedComposition' default: description: Error headers: Request-Id: description: Identifier for this request, quote it in support tickets. schema: type: string content: application/problem+json: schema: $ref: '#/components/schemas/Problem' security: - Bearer: [] components: schemas: DeletedComposition: type: object properties: object: type: string enum: - composition description: Always `composition`. id: type: string description: The id of the deleted object. deleted: type: boolean enum: - true description: Always `true`. required: - object - id - deleted Problem: type: object properties: type: type: string description: A URI naming the problem type. Always `about:blank`. example: about:blank title: type: string description: A short summary of the HTTP status. example: Not found status: type: integer description: The HTTP status code. example: 404 detail: type: string description: What went wrong with this request, when there is more to say. code: type: string description: >- A stable, machine-readable error code to branch on, unlike `title` and `detail`. example: not_found param: type: string description: The request field or parameter the error is about, when one is. request_id: type: string description: >- The id of the request, also sent as the `Request-Id` header. Quote it in support tickets. example: req_9f2b8c1d4e5a6b7c8d9e0f1a2b3c4d5e required: - type - title - status - code securitySchemes: Bearer: type: http scheme: bearer bearerFormat: Tightknit API key description: 'A Tightknit admin API key, sent as `Authorization: Bearer `.' ```` ## Related topics - [Delete a composition delivery](https://docs.tightknit.ai/v1/api-reference/compositions/delete-a-composition-delivery.md) - [MCP Server](https://docs.tightknit.ai/integrations/mcp.md) - [List compositions](https://docs.tightknit.ai/v1/api-reference/compositions/list-compositions.md) - [Retrieve a composition](https://docs.tightknit.ai/v1/api-reference/compositions/retrieve-a-composition.md) - [Update a composition](https://docs.tightknit.ai/v1/api-reference/compositions/update-a-composition.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.