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

DELETE /trigger/triggers/{trigger_type}/{topic}

Delete a trigger

cURL

curl --request DELETE \
  --url https://api.quiva.ai/trigger/triggers/{trigger_type}/{topic} \
  --header 'Authorization: Bearer <token>'

200

{
  "status_code": 200
}

Authorizations

Authorization · string · header · required

JWT token for authentication. Required for all API operations to verify identity and access permissions.

Path Parameters

trigger_type · enum<string> · required

The type of trigger (gateway, stream, subject)

Available options: gateway, stream, subject

topic · string · required

The unique topic identifier of the trigger (without the prefix)

Response

200

application/json

Successfully deleted trigger

status_code · integer

HTTP status code indicating success

Example:

200