> ## Documentation Index > Fetch the complete documentation index at: https://microstrate-1133-notifications-prefs.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Delete a trigger > Marks a trigger as deleted (poison-pilled). This operation logically removes the trigger from the system while preserving the record. **Usage Notes:** - This operation cannot be undone through the API - The `trigger_type` and `topic` parameters together identify the exact trigger to delete - The system constructs the full subject using these parameters: `ms.trigger.{trigger_type}.{topic}` - For gateway triggers, associated mappings remain but are no longer accessible - For stream triggers, connections between source and target are terminated - In-flight operations may still complete, but new operations will be rejected - The trigger remains in the system's history for audit purposes ## OpenAPI ````yaml /api-reference/endpoint/trigger/openapi.json delete /trigger/triggers/{trigger_type}/{topic} openapi: 3.0.3 info: title: quiva.ai Gateway description: >- # Bellerophon Trigger Service API The Trigger Service is a Bellerophon API service that provides an interface for managing various types of triggers through a subject-based messaging system. This API allows you to create, retrieve, and delete different types of triggers including gateway and stream triggers. ## Core Concepts ### Triggers Triggers are the foundation of the Bellerophon platform's event-driven architecture. A trigger connects different parts of the system, allowing events in one component to initiate actions in another. Each trigger has a unique subject identifier that follows a specific naming pattern. ### Gateway Triggers Gateway triggers create API endpoints that can be accessed from outside the system. They define HTTP methods, paths, rate limits, and connect incoming requests to processing functions. ### Stream Triggers Stream triggers connect data sources to targets, enabling real-time data flow between components. They define how data should be processed, transformed, and routed within the system. ## Subject Structure The service follows a subject naming pattern which typically expands to: ``` ms.trigger.[trigger_type].[resource_name] ``` All API endpoints use the /trigger/ prefix in their paths for consistency and to clearly identify the trigger service. contact: name: Bellerophon Support version: '1.0' servers: - url: https://api.quiva.ai description: Production API server security: - bearer_auth: [] paths: /trigger/triggers/{trigger_type}/{topic}: delete: tags: - Triggers summary: Delete a trigger description: >- Marks a trigger as deleted (poison-pilled). This operation logically removes the trigger from the system while preserving the record. **Usage Notes:** - This operation cannot be undone through the API - The `trigger_type` and `topic` parameters together identify the exact trigger to delete - The system constructs the full subject using these parameters: `ms.trigger.{trigger_type}.{topic}` - For gateway triggers, associated mappings remain but are no longer accessible - For stream triggers, connections between source and target are terminated - In-flight operations may still complete, but new operations will be rejected - The trigger remains in the system's history for audit purposes operationId: deleteTrigger parameters: - name: trigger_type in: path description: The type of trigger (gateway, stream, subject) required: true schema: type: string enum: - gateway - stream - subject example: gateway - name: topic in: path description: The unique topic identifier of the trigger (without the prefix) required: true schema: type: string example: my-gateway-trigger responses: '200': description: Successfully deleted trigger content: application/json: schema: type: object properties: status_code: type: integer description: HTTP status code indicating success example: 200 example: status_code: 200 '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalServerError' components: responses: BadRequest: description: >- Invalid request. Occurs when required parameters are missing, validation fails, or the request format is incorrect. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: >- Invalid request: Missing required field 'name' in trigger definition status_code: 400 Unauthorized: description: >- Unauthorized access. Occurs when authentication is missing or invalid, or when the authenticated user lacks permission. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: 'Unauthorized: Invalid or missing authentication token' status_code: 401 NotFound: description: >- Resource not found. Occurs when attempting to access a trigger or resource that doesn't exist or has been deleted. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: >- Not found: The requested trigger with topic 'my-trigger' does not exist status_code: 404 InternalServerError: description: >- Internal server error. Occurs when an unexpected condition prevents the server from fulfilling the request. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: 'Internal server error: Unable to process request at this time' status_code: 500 schemas: Error: type: object properties: error: type: string description: >- Detailed error message explaining what went wrong and potential solutions. example: 'Invalid request: Missing required field' status_code: type: integer description: HTTP status code indicating the specific error type. example: 400 securitySchemes: bearer_auth: type: http scheme: bearer bearerFormat: JWT description: >- JWT token for authentication. Required for all API operations to verify identity and access permissions. ````