---
title: "Retrieve all triggers"
method: GET
path: "/trigger/triggers"
tags: ["Triggers"]
---

# Retrieve all triggers

`GET /trigger/triggers`

## Request

- Base URL: `https://api.quiva.ai`
- URL: `https://api.quiva.ai/trigger/triggers`
- Auth: one of:
  - HTTP bearer
  - API key in header `x-api-key`
- TypeScript: <https://skmtc.dev/quivaworks/apis/quiva-ai-gateway-6/docs/trigger/triggers/get.ts> (a function with typed inputs; its response is checked against the schema)

Retrieves all triggers matching a specific subject pattern. This endpoint provides a comprehensive view of all available triggers that match the given pattern, including their configurations, types, and associated metadata.

**Usage Notes:**
- Use wildcards in the subject pattern to match multiple triggers
- Results include all trigger types (gateway, stream, subject)
- Each trigger includes its complete configuration
- The subject pattern forms part of the unique identifier for triggers
- The response includes total count of matching triggers

## Query parameters

- `subject_pattern` string, required

## Response `200`

Successfully retrieved triggers

- TriggerListResponse
  - `body` object
    - `results` TriggerData[]: Array of trigger data objects matching the query criteria.
      - `name` string, required: Unique name identifier for the trigger. Used to construct the trigger's topic and subject.
      - `collection` string: Logical grouping the trigger belongs to. Used for organizing and filtering triggers.
      - `description` string: Human-readable description explaining the trigger's purpose and function.
      - `gateway_mapping_subject` string: Full subject identifier assigned to the gateway mapping. Only present for gateway triggers.
      - `stream` string: Stream identifier where the trigger configuration is stored, typically "quiva-trigger-config".
      - `subject` string: Full subject identifier for the trigger, following the pattern "ms.trigger.[type].[name]".
      - `trigger_type` 'gateway' | 'stream' | 'subject', required: Category of trigger determining its behavior and available properties.
      - `type` string: Specific type identifier providing additional classification information.
      - `source` TriggerSource
        - `advertise` boolean: Whether to advertise this trigger source to other services. When true, allows other services to discover this source.
        - `allow_trace` boolean: Whether to allow request tracing. When true, enables debugging and performance monitoring.
        - `name` string: Human-readable name for the source. Used for identification in logs and monitoring.
        - `response_type` 'Singleton' | 'Stream' | 'Chunked': Format of response data from this source: * Singleton - Returns a single response and closes * Stream - Continuously streams data until connection closes * Chunked - Returns paginated data in multiple responses
        - `subject` string: Subject identifier for the source. Used for routing messages to/from this source.
        - `type` 'stream' | 'service': Export type categorizing how this source behaves: * stream - Emits a continuous flow of data * service - Provides request/response functionality
        - `description` string: Detailed information about the source including its purpose and data format.
        - `info_url` string: URL pointing to additional documentation or information about this source.
      - `target` TriggerTarget
        - `name` string: Human-readable name for the target. Used for identification in logs and monitoring.
        - `subject` string: Subject identifier for the target. Used for routing messages to this target.
        - `account` string: Account identifier owning or associated with this target. Used for access control.
        - `local_subject` string: Alternative subject for local routing within the same account.
        - `type` 'stream' | 'service': Export type categorizing how this target behaves: * stream - Consumes a continuous flow of data * service - Provides request/response functionality
        - `share` boolean: Whether this target is shareable with other accounts. When true, allows cross-account access.
        - `allow_trace` boolean: Whether to allow request tracing to this target. When true, enables debugging and performance monitoring.
    - `results_total` integer: Total count of triggers matching the query criteria.
  - `metadata` object
    - `subject` string: Subject pattern used for the query. May contain wildcards.
  - `status_code` integer: HTTP status code indicating the result of the operation.

## Other responses

- `400`: Invalid request. Occurs when required parameters are missing, validation fails, or the request format is incorrect.
- `401`: Unauthorized access. Occurs when authentication is missing or invalid, or when the authenticated user lacks permission.
- `500`: Internal server error. Occurs when an unexpected condition prevents the server from fulfilling the request.

---

[API](https://skmtc.dev/quivaworks/apis/quiva-ai-gateway-6.md) - [All operations](https://skmtc.dev/quivaworks/apis/quiva-ai-gateway-6/llms.txt) - [OpenAPI document](https://skmtc.dev/quivaworks/apis/quiva-ai-gateway-6/revisions/a9f443efdc5d?raw)